What you call "branch" is the JNDI name of the queue. If you deploy a queue using the org.jboss.mq.server.jmx.Queue MBean, the JNDI name of the queue is derived from the MBean "name" attribute, ie
| <server> | <mbean code="org.jboss.mq.server.jmx.Queue" | name="jboss.mq.destination:service=Queue,name=customqueue/TestQueue"> | <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends> | </mbean> | </server> | will bind the queue at "customqueue/TestQueue". If you want very special JNDI names (ie if they contain ":" which is not allowed inside the MBean name), use the optional attribute | <attribute name="JNDIName">customqueue/TestQueue:1</attribute> | Actually, you can bind the queue even to several names in JNDI: just lookup() the queue using a JNDI name and bind() the result to another one. The "queue/" location is just default location, I am not aware of further consequences if you do not use it. Cheers, Jörg View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3887868#3887868 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3887868 ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
