The JBoss Messaging guys (you have them to blame for this :) suggested I refer this issue to you. In JBoss 4.2.3.GA, I was able to declare my queues like this... <mbean code="org.jboss.mq.server.jmx.Queue" | name="jboss.mq.destination:service=Queue,name=my-app/imports1"> | ... | </mbean> ...but this gives an error in 5.1.0.GA that the namespace 'my-app' is not bound. The error is correct, it is not bound, but in 4.2.3.GA JBoss would automatically create it for me. In 5.1.0.GA, I have to do... <mbean code="org.jboss.jms.server.destination.QueueService" | name="jboss.messaging.destination:service=Queue,name=my-app-imports1" | ... | </mbean> ...so therefore my-app-imports1 does not enjoy the same JNDI 'heirarchy' as my-app/imports1. Is this intentional to a new spec? Thanks in advance, Richard. P.S. The original forum thread is here: http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237550#... View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238065#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...