"ataylor" wrote : anonymous wrote : Ok good. What are the JMSExample::deployQueues and deployTopics for though? | | My initial thought was to deploy the queues if they didn't already exist, say if the user ran against a standalone server. If your happy to stipulate that they should only be in the config then thats fine. I'll remove it and make things easier. | +1 The simpler the better anonymous wrote : | Just one point, the config in the actual examples, i.e. examples/jms/queue/config, is also added to the classpath when run. We should add any extra queues etc in here, I notice theres an expiry queue in the common config, this should be moved and we only have the basic in exampleQueue and exampleTopic in this one. To clarify, the classpath for each example first contains the example/jms/<example_name>/config dir followed by the example/jms/common/config dir ? So we can just override anything already in each example? If each example can provide its own config is there any value in a common config? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223192#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...