Hello. It is causing me problems that the destination activation config property is mandatory for MDB's. I was wondering if anyone has solutions or tricks on how to solve them. In my deployment scenario I don't know the queue name (i.e. destination) until just prior of load time of my mdb's, i.e. it is unknown at compile time. Is there a way to solve this? Also, there may very well be cases where messages that can be handled by the same mdb implementation arrive on different queues, is it possible to deploy an mdb multiple times to receive messages from separate queues? Or can't I use mdb's at all if these are my requirements? Thanks / Jonas View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029133#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...