<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Tue, Aug 25, 2015 at 9:51 AM Nigel Deakin <<a href="mailto:nigel.deakin@oracle.com">nigel.deakin@oracle.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 24/08/2015 21:24, John D. Ament wrote:<br>
><br>
> Hi Nigel!<br>
><br>
> Glad to hear from you. Was wondering, is there a way to manually register listeners?<br>
<br>
The current proposal is is for the bean to start listening just as soon as it is created (by CDI), and for it to stop<br>
listening just before it is destroyed (by CDI).<br>
<br>
As you suggesting that CDI would create the listener, but the application would call some method to tell it to start<br>
listening? or did you have something else in mind?<br></blockquote><div><br></div><div><br></div><div>Hmm, this would mean that only app scoped beans would apply?</div><div>It might be better to scan for the annotations and use that to start up the listener?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
> It would be great if this could<br>
> be leveraged in a CDI SE environment as well as EE environment.<br>
<br>
I see that work is underway for CDI 2.0 to define how CDI might work in a Java SE environment. I don't see why a similar<br>
portable extension could not be created for use in Java SE. Since there would be no need to support Java EE behaviour<br>
such as transactions this could be built directly on top of the JMS provider's Java SE client. No need to use a resource<br>
adapter. However since the @JMSListener and @JMSConnectionFactory annotations use JNDI there would be a need to be a way<br>
to specify which JNDI InitialContext to use. I'm not proposing any of this at the moment, but it might perhaps be<br>
something that we (the JMS expert group) could consider later on as a optional part of JMS 2.1.<br>
<br>
There's also the Java EE application client to consider.<br>
<br>
Nigel<br>
<br>
</blockquote></div></div>