[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1667) MBeans cannot have heirarchical names

[Tim Fox (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBMESSAGING-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12473726#action_12473726 ] 

Tim Fox commented on JBMESSAGING-1667:
--------------------------------------

JBM, ActiveMQ, also any AMQP based system will use dots. JBM 2.0 uses dots too. (see http://www.jboss.org/file-access/default/members/jbossmessaging/freezone/docs/usermanual-2.0.0.beta3/html/wildcard-routing.html )

Using slashes won't allow you to exploit wildcard routing in JBM 2.0 (or ActiveMQ or many other systems for that matter).

I recommend for this task we keep the behaviour as is and explicitly disallow the forward slash character in destination names. We can throw a warning on deploy and not deploy them if they contain the forward slash character.

I am loathed to give special status to the forward slash character that would make it create subcontextes automatically since this goes against the grain of normal conventions for topic hierarchies.

> MBeans cannot have heirarchical names
> -------------------------------------
>
>                 Key: JBMESSAGING-1667
>                 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1667
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: JMS Destination Manager
>    Affects Versions: 1.4.0.SP3.CP08, 1.4.4.GA
>         Environment: JBoss 5.1.0.GA
>            Reporter: Richard Kennard
>            Assignee: Howard Gao
>             Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
>
>
> In JBoss 4.2.3.GA, it was possible to declare queues with 'heirarchical' names, for example:
> <mbean code="..." name="...,name=app1/emails">
> The forward slash in 'app1/emails' created a nested JNDI context of 'queue/app1/emails'. In JBoss 5.1.0.GA this no longer works. JBoss fails saying that the top-level context 'app1' does not exist. This is true, but JBoss should create it just-in-time.
> A workaround proposed on the forums is to use the 'JNDIName' attribute:
> <mbean code="..." name="...,name=emails">
>    <attribute name="JNDIName">app1/emails</attribute>
> This works from a JNDI perspective, but the mbean itself is still named just 'emails' leaving the potential for name clashes:
> <mbean code="..." name="...,name=emails">
>    <attribute name="JNDIName">app1/emails</attribute>
> <mbean code="..." name="...,name=emails">
>    <attribute name="JNDIName">app2/emails</attribute>
> In JBoss 4.2.3.GA it was possible to declare queue names safely nested within their own heirarchies to avoid the possibility of name clashes. It would be nice to have this in JBoss 5.1.0.GA too.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira