You want the same MDB implementation to listen to multiple queues?
I don't think that's really possible (not in the same application at least, perhaps installed in several different EARs...).
There's really only "one" MDB in your application. There may be several instances, each processing their own message, but they're all listening to the same queue/topic. But the construct as a whole is a single entity.
You pretty much need several MDBs, one for each queue/topic. If they share code, you can refactor it out in to a common set of classes, or perhaps a Session Bean.
[Message sent by forum member 'whartung' (whartung)]
http://forums.java.net/jive/thread.jspa?messageID=244402