[cdi-dev] JMS 2.1: Proposal to allow any CDI managed bean in a Java EE application to listen for JMS messages

Nigel Deakin nigel.deakin at oracle.com
Wed Aug 26 05:07:01 EDT 2015

(Tidying up the top-posting...)

Romain Manni-Bucau:
 > ...I see it really nice to not rely only on annotation - and aligned with
 > most specs - since sometimes you just want to either be able to rely on a
 > loop or a custom config to register your listeners. Annotations are too
 > rigid for such cases.

 > Obviously, if users don't want to use CDI (or MDBs, which are also
 > declarative), then they would use the  normal JMS API. The existing
 > API to register an async message listener isn't good enough,
 > and we may improve it in JMS 2.1, but that's not something that
 > I'd want to bother the people on cdi-dev with.

Romain Manni-Bucau:
 > Integrating it in CDI lifecycle through an event allow CDI users to still
 > use it in the right phase of the container boot so it is still important
 > IMO and avoid all users to have their own custom listener for it -
 > @Initialized(AppScoped.class). Also allow to enrich the API through the event
 > itself making things smoother IMO.

 > I'm sorry I don't understand you.
 > I thought you were asking about an API which does not use annotation.

Romain Manni-Bucau:
 > Both are needed (like websocket spec). Annotation one is nice for fully business
 > code and/or simple libs but relying on CDI allows to simplify the wiring since you
 > can reuse CDI beans under the hood ie have an implicit connection factory if
 > there is a single one etc which is not possible in fully SE context.

Can you explain the distinction you're making here? You seem to be suggesting two alternatives, using "annotation" and 
"relying on CDI". What would an application which uses CDI but which doesn't use annotation look like?


More information about the cdi-dev mailing list