You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Alan Cabrera (JIRA)" <ji...@apache.org> on 2010/06/18 07:05:22 UTC

[jira] Created: (FELIX-2422) /a/b/c/* should match topic /a/b/c

/a/b/c/* should match topic /a/b/c
----------------------------------

                 Key: FELIX-2422
                 URL: https://issues.apache.org/jira/browse/FELIX-2422
             Project: Felix
          Issue Type: Bug
          Components: Event Admin
    Affects Versions: eventadmin-1.2.2
            Reporter: Alan Cabrera


/a/b/c/* should match topic /a/b/c

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (FELIX-2422) /a/b/c/* should match topic /a/b/c

Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-2422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved FELIX-2422.
-------------------------------------

    Resolution: Invalid

I understand the spec differently. The star is a placeholder for the last part of the path, therefore the above matches only topics that start with /a/b/c/...

>From the spec:
Event handlers should be registered with a property (constant from the 
EventConstants class) EVENT_TOPIC. The value being a String or String[] 
object that describes which topics the handler is interested in. A wildcard ('*' 
\u002A) may be used as the last token of a topic name, for example com/ 
action/*. This matches any topic that shares the same first tokens. For 
example, com/action/* matches com/action/listen. 


Closing this as invalid

> /a/b/c/* should match topic /a/b/c
> ----------------------------------
>
>                 Key: FELIX-2422
>                 URL: https://issues.apache.org/jira/browse/FELIX-2422
>             Project: Felix
>          Issue Type: Bug
>          Components: Event Admin
>    Affects Versions: eventadmin-1.2.2
>            Reporter: Alan Cabrera
>
> /a/b/c/* should match topic /a/b/c

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (FELIX-2422) /a/b/c/* should match topic /a/b/c

Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-2422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler closed FELIX-2422.
-----------------------------------

    Resolution: Invalid

As discussed on the osgi-dev list, BJ Hargrave confirmed that our implementation is correct - therefore closing this bug

> /a/b/c/* should match topic /a/b/c
> ----------------------------------
>
>                 Key: FELIX-2422
>                 URL: https://issues.apache.org/jira/browse/FELIX-2422
>             Project: Felix
>          Issue Type: Bug
>          Components: Event Admin
>    Affects Versions: eventadmin-1.2.2
>            Reporter: Alan Cabrera
>
> /a/b/c/* should match topic /a/b/c

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Reopened: (FELIX-2422) /a/b/c/* should match topic /a/b/c

Posted by "Alan Cabrera (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-2422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alan Cabrera reopened FELIX-2422:
---------------------------------


The example they give is not meant to be exhaustive.  The key phrase is "This matches any topic that shares the same first tokens".  This is how other OSGi frameworks work.

> /a/b/c/* should match topic /a/b/c
> ----------------------------------
>
>                 Key: FELIX-2422
>                 URL: https://issues.apache.org/jira/browse/FELIX-2422
>             Project: Felix
>          Issue Type: Bug
>          Components: Event Admin
>    Affects Versions: eventadmin-1.2.2
>            Reporter: Alan Cabrera
>
> /a/b/c/* should match topic /a/b/c

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.