2.3. JBoss Messaging

Hierarchical MBean Names

The version of JBoss Messaging included in JBoss Enterprise Application Platform 4.3 allowed users to declare message queues with hierarchical names such as app1/emails, where the forward slash would create a nested JNDI context of queue/app1.emails. This behavior prevents name clashes between applications with similarly-named queues:

<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app1/emails</attribute>

<mbean code="..." name="...,name=emails">
<attribute name="JNDIName">app2/emails</attribute>
This behavior is now included in JBoss Enterprise Application Platform 5.0.1. However, the syntax has been altered to allow users to exploit wildcard routing in future versions of JBoss Messaging. The point "." should be used instead of the forward slash, "/", like so:
<mbean code="..." name="...,name=app1.emails">
<attribute name="JNDIName">app1.emails</attribute>

<mbean code="..." name="...,name=app2.emails">
<attribute name="JNDIName">app2.emails</attribute>