The way I have refactored (soon to commit) is as follows: All the JMS stuff (I think) is now on the client side in the thin client layer, we also have a pure core client. The session has methods to createQueue and createConsumer. creating a queue would be done when a) creating a jms queue b) creating a topic subscription c) creating a temporary queue these are all queues. As you mention, by default queues should be created as long the user has the CREATE permission for that point in the condition name. JMS TCK also requires that some queues are pre-deployed. This can be supported by the JNDIDeployer - which we should probably rename to JMSServerManager. This component should expose a JMS centric management API which then calls the pure core managermenent api of the core server. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4127026#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...