Hello All,
Attached are documents containing my proposal for CDI support in JMS 2.0.
There are two documents:
1. JMS2.0AtInjectSupport - this document describes basic injection
capabilities that are desirable to JMS 2.0. These injection capabilities
allow for the injection of the standard JMS client APIs into any managed
object within a bean archive. This document also describes some minor API
changes that I believe would help simplify development.
2. JMS2.0EventMessaging - this document describes a mapping process from
POJOs to JMS Messages, usage of the CDI Event model API to send events that
were observed as JMS messages to specified destinations and to handle
incoming JMS messages as CDI events.
I started to put these up on the wiki, however the formatting support in the
wiki doesn't seem to be there for how I was looking to structure the
documents, but I'll work on getting them in; I really wanted to get the
documents out there as I work with the wiki. I recommend reading these
documents in the numbered order as listed in this email. I tried very hard
to not make them dependent on one another, however there are some shared
contents between them. It makes sense to support both if either is chosen
for support, however there is no required behavior between the documents
that is no touched upon by both. I'm not sure what the process should be
for review, but I figure we should set a time limit on the review period,
maybe 2 weeks? (Nigel, I hope you can provide some feedback on a timeline,
since one of the issues we noted on the call was a time frame for draft). I
assume all comments should be posted back to the EG, If anyone would like to
ask me specific questions related to CDI, I assume it's fine to ask
directly. As a note, these should be considered in parallel to Reza's
documentation on a Spring-styled API.
Regards,
John