I would like to propose the following for JBM 2.0 declarative queue security and destination settings overrides. I believe it is more elegant and flexible than the current 1.x approach. Note that in JBM 2.0 messaging core, *everything* is a queue - core does not know about JMS topics and queues. A JMS queue is a queue and a JMS topic subscription is also a queue. A JMS queue has a name something like: | | queues.acme.orderprocessing.inputqueue1 | | A JMS topic subscription is just a queue with a name something like: | | topics.acme.marketdata.RHAT.xyz123 | | or | | topics.acme.newsfeed.europe.* | | The declarative security is hierarchical and can work with wildcards. E.g. | | <!-- default - deny all creates --> | <security match="queues.*"> | ... | </security> | | <security match = "queues.finance.stocks.*"> | <permission="read", roles="all"> | <permission="write", roles="admin"> | </security> | | We should also allow the ability to specify groups of override settings for groups of queues, e.g. | e.g. | | <queue-settings match="queues.stocks.*"> | <max-size>10000</max-size> | <no-persistence>true</no-persistence> | <lazy-load>true</lazy-load> | </queue-settings> | | This should probably go in a file called queues.xml which is loaded by core on startup. The file should be hot deployable. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117491#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...