It it safe to use SJMS or JMS in a Java EE 6 application?

You are not supposed to start threads in Java EE, but (S)JMS uses
thread pools for consumers. Is it guaranteed that features like
resource or CDI injection, CDI scopes, JNDI lookup will work in these
these threads just the same as in a container-managed thread?

Isn't it true that MDBs are the only official way to asynchronously
consume JMS messages in a Java EE application? Does SJMS have any
adapters for MDBs?

(I'm mainly interested in SJMS, but I believe the same issues apply to
the Spring-based JMS component.)

Best regards,
Harald

Reply via email to