<div dir="ltr">All,<div><br></div><div>Especially if it was only relevant to some "profile" of CDI or environment like SE, I'd say </div><div>+1 for Option 1.</div><div><br></div><div>It sounds more modular to me, e.g. this sub-class may only appear in a certain module of CDI 2 and above (even more vital when you think SE 9+ and Jigsaw;-)</div><div><br></div><div>Cheers,<br><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><p style="margin:0px;font-size:13px;border-collapse:collapse"><span lang="EN-US" style="font-family:Calibri">Werner </span></p><span lang="EN-GB"></span></div></div></div></div></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On Wed, Mar 25, 2015 at 7:14 AM, <span dir="ltr"><<a href="mailto:cdi-dev-request@lists.jboss.org" target="_blank">cdi-dev-request@lists.jboss.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send cdi-dev mailing list submissions to<br>
<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:cdi-dev-request@lists.jboss.org">cdi-dev-request@lists.jboss.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:cdi-dev-owner@lists.jboss.org">cdi-dev-owner@lists.jboss.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of cdi-dev digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. JavaLand (Thorben Janssen)<br>
2. Re: JavaLand (Mark Struberg)<br>
3. Today's meeting --> Focus on Java SE (Antoine Sabot-Durand)<br>
4. Shutting down CDI Instances (John D. Ament)<br>
5. Some more thoughts on async events (Jos? Paumard)<br>
6. Re: Some more thoughts on async events (Mark Struberg)<br>
7. Re: Some more thoughts on async events (Antoine Sabot-Durand)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 4<br>
Date: Tue, 24 Mar 2015 18:00:00 +0000<br>
From: "John D. Ament" <<a href="mailto:john.d.ament@gmail.com">john.d.ament@gmail.com</a>><br>
Subject: [cdi-dev] Shutting down CDI Instances<br>
To: "<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a>" <<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a>><br>
Message-ID:<br>
<<a href="mailto:CAOqetn_wThUpYSb_2D%2BVTBaq3MAd4MVn6FqX9aHa444XkvM9Yg@mail.gmail.com">CAOqetn_wThUpYSb_2D+VTBaq3MAd4MVn6FqX9aHa444XkvM9Yg@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
All,<br>
<br>
In discussion today w/ Jozef, we found that the way of shutting down a<br>
container in the proposed SE API precluded the notion that multiple<br>
containers could be running. While we're not necessarily going to handle<br>
multiple containers right now, we don't want to preclude the idea either.<br>
With that said, there were three different approaches though up to handle<br>
how to shutdown a launched container. it obivously would only work with an<br>
SE booted container, but part of this does give a pointer in how we may<br>
implement initialize.<br>
<br>
Option 1 - Subclass CDI. The returned CDI instance when bootstrapped would<br>
return this subclass of CDI that has shutdown capability.<br>
<br>
Option 2 - Add method to CDI. Add the shutdown method to CDI directly, and<br>
throw an exception if called in an EE environment.<br>
<br>
Option 3 - Return a different object all together when initializing.<br>
Return something else from initialize, e.g. CDIContext, which has a<br>
shutdown method when you initialize. That class would also have a getter<br>
for the CDI instance backing it.<br>
<br>
Let us know your thoughts.<br>
<br>
Thanks,<br>
<br>
John<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://lists.jboss.org/pipermail/cdi-dev/attachments/20150324/096f96d5/attachment-0001.html" target="_blank">http://lists.jboss.org/pipermail/cdi-dev/attachments/20150324/096f96d5/attachment-0001.html</a><br><br>
_______________________________________________<br>
cdi-dev mailing list<br>
<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
<br>
Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 (<a href="http://www.apache.org/licenses/LICENSE-2.0.html" target="_blank">http://www.apache.org/licenses/LICENSE-2.0.html</a>). For all other ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.<br>
<br>
End of cdi-dev Digest, Vol 52, Issue 82<br>
***************************************<br>
</blockquote></div><br></div></div></div>