Hi all,

I have a problem understanding how (assembled and tested) ejb-archives containing MDBs can be deployed in multiple applications without avoiding resource conflicts. To my knowledge, queues are bound (either by xml or annotations) when assembling the module (EJB) and not when assembling the application (EAR)...?

Servlet context can be bound on application level, global JNDI names for SLSBs can be generated on application level (referencing them with ENC). persitence.xml file can be application-defined which isolate datasources from eachother and overcome conflicts for reused entity beans.

But, for MDBs i have not found any similar way of lately bind a MDB to application-defined queues?

Cheers,
-Kristoffer