I take it container discovery and validation still happens at startup even
for these CDI listeners?
Is there anything that can be added to allow an @SessionScoped listener
that only delivers messages for the current session? I think that will be a
more common reason to use a @SessionScoped jms listener (i.e only deliver
when user session exists AND only messages intended for the current user).
Would adding a message selector callback approach be too much work for
container developers for too little gain?
Kind regards
Evans Armitage.
On 25 Aug 2015 1:39 PM, "Josh Juneau" <juneau001_at_gmail.com> wrote:
> Nigel-
>
> I am very pleased to see the proposed changes to the JMS MDBs. The
> changes will help JMS to evolve even further, making the API easier to
> learn and use. MDBs have been one of those constructs that may be deemed
> difficult to use or understand by beginners. The proposed changes make JMS
> MDBs easier to understand and more flexible, providing the ability to
> develop more sophisticated solutions.
>
> In particular, I am glad to see the proposed change that removes the
> requirement to implement javax.jms.MessageListener, as it can sometimes
> limit the functionality, making JMS MDBs cumbersome to use. Providing the
> ability to define more than one callback method per MDB will increase the
> flexibility of MDBs.
>
> I'll review in more detail as time allows, and provide further feedback.
> At this time I see the proposed changes as a very positive move in the
> right direction.
>
> Best
>
> Josh Juneau
> juneau001_at_gmail.com
> http://jj-blogger.blogspot.com
> https://www.apress.com/index.php/author/author/view/id/1866
>
>
> On Tue, Aug 25, 2015 at 6:13 AM, Rahman USTA <rahman.usta.88_at_gmail.com>
> wrote:
>
>> Hello Nigel;
>>
>> I think, the proposed suggestion seems quite well.
>>
>> 2015-08-25 13:48 GMT+03:00 Nigel Deakin <nigel.deakin_at_oracle.com>:
>>
>>> On 24/08/2015 15:51, Nigel Deakin wrote:
>>>
>>>>
>>>> To start things off, I've written down some proposals which you can
>>>> read at
>>>> https://java.net/projects/jms-spec/pages/CDIBeansAsJMSListeners
>>>>
>>>
>>> Although this is a JMS feature (and would end up in the JMS spec), it is
>>> based on CDI so I've invited people on the CDI spec mailing list (which
>>> anyone can join) to make comments and suggestions as well from a CDI
>>> perspective.
>>>
>>> I'm aware that most of us here, me included, are more familiar with JMS
>>> than with CDI.
>>>
>>> A little discussion has started, which you can read here:
>>>
>>> http://cdi-development-mailing-list.1064426.n5.nabble.com/JMS-2-1-Proposal-to-allow-any-CDI-managed-bean-in-a-Java-EE-application-to-listen-for-JMS-messages-tt5711848.html#none
>>>
>>> However the principal place to make comments on this proposal is still
>>> here (users_at_jms-spec.java.net and jsr368-experts_at_jms-spec.java.net
>>> which forwards to it).
>>>
>>> Nigel
>>>
>>>
>>
>>
>> --
>> Rahman USTA
>> Istanbul JUG
>> https://github.com/rahmanusta <http://www.kodcu.com/>
>>
>
>