I am in favor of (for somewhat obvious reasons) of binding received
messages to CDI events. However, I think to do it in an EE scenario will
require some JCA changes, or some deployment changes for MDBs.
John
On Thu, Mar 29, 2012 at 9:29 AM, Nigel Deakin <nigel.deakin_at_oracle.com>wrote:
> (Starting a new thread for this issue, and sent to correct list this time)
>
>
> Rüdiger,
>
> On 29/03/2012 12:01, Rüdiger zu Dohna wrote:
>
>> On 2012-03-29, at 12:27, Nigel Deakin wrote:
>>
>>>
>>>> You offer two alternatives.
>>>
>>> 1. Binding to CDI events.
>>>
>>> In this, you are defining a listener on a CDI event. How is this related
>>> to JMS? Are you suggesting that when a JMS
>>> message is received the JMS provider automatically fires a CDI event
>>> containing the message payload?
>>> If not, what are you suggesting?
>>>
>>
>> Yes, exactly. The same would work for the sender as well,
>> and the only thing the business code _has_ to care about,
>> is one annotation on the event type.
>> Everything else has useful defaults.
>>
>
> So how would the incoming JMS message be converted into a CDI event? Are
> you proposing a standard mechanism for doing this?
>
> 2. Binding to a business interface
>>>
>>> Is this essentially the MessageAPI approach (which you kindly explained
>>> to me when we met in Belgium)?
>>>
>>
>> Exactly! Only that I've explained it from the receiver side this time.
>>
>
> OK. Initially I'd like to find out whether these are two separate
> proposals, or whether the first is actually a way to express MessageAPI in
> terms of CDI events.
>
> Nigel
>
>
>