On 22/07/2011 08:34, Rüdiger zu Dohna wrote:
> Nigel,
>
> On 07/21/2011 04:38 PM, Nigel Deakin wrote:
>> I've received no objections so far to either:
>> (1) defining some more JMS-specific mandatory activation config properties and
>> (2) a new @JMSMessageDriven annotation with such properties available as attributes.
>
> Does anybody know of any (more than experimental) adapter to @MessageDriven other than JMS? I'd argue that this is an
> unnecessary abstraction, considering that JMS itself is already meant to abstract from all messaging systems!
Just to pick one product I worked on a few years ago, Oracle Java CAPS (a SOA product) has implemented a large number of
resource adapters which deliver various incoming events as asynchronous MDB callbacks, and which are a fundamental part
of the product architecture. In addition to JMS messages, they allow MDBs to be used to handle incoming emails, SWIFT
messages, HL7 messages, HTTP requests, files delivered by ftp, files arriving in a watched directory, updates from
various databases, etc. There's even a do-it-yourself kit to allow customers to write their own resource adapter to
allows MDBs to be used with new types of event.
So although JMS is certainly an important use case for MDBs (which is why it is mentioned in the MDB spec), MDBs are
intended to support other types of asyncronous event as well.
Nigel