<div dir="ltr">Dear Antoine/all,<div><br></div><div>Thanks for the detailed overview and trying to reach out to the former Spec Leads and EG of JSR 330. I also copied Anatole, Spec Lead of JSR 354, since Bob Lee is officially in his EG, but has practically never provided input there either (like we tend to see sometimes from others considered "Rock Stars" of the Java Community but since then seemingly resting on their laurels or just too busy counting their stock options?<img src="cid:329@goomoji.gmail" goomoji="329" style="margin: 0px 0.2ex; vertical-align: middle;">) </div>
<div><br></div><div>Given CDI already was the public perception of "javax.inject" for most parts, I don't necessarily see that it had to be an MR to the original JSR, though as those involved in the EC (Martijn, Badr/MoroccoJUG,..) could probably check with the PMO how to handle a case where the Maintenance Lead of a JSR was not in the position to continue. I last met Jürgen Höller about a year ago in Copenhagen, so for Pivotal's part as Co Spec Lead, I guess he or the likes of Josh Long could be best to speak to. Happy to get you in touch with them if you want.</div>
<div><br></div><div>Red Hat was also EG member of JSR 330, so Pete, Gavin or whoever else was there (I remember him from conversations where Mike Keith and I took part in synergy discussions between 330 and CDI 1.0) at the time could also help you with this.</div>
<div><br></div><div>In theory this could also be part of a new JSR (CDI 2) as long as none of the enhancements you have in mind break the existing API of JSR 330. The scope of CDI 2 to work in an SE/standalone or more lightweight environment than Java EE environment raises a good question of package names like "<span style="font-family:arial,sans-serif;font-size:13px"> </span><span style="font-family:arial,sans-serif;font-size:13px">javax.enterprise.inject.*" So maybe there is room for synergies in a package namespace other than "javax.enterprise" at least for new things you have in mind.</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div>Kind Regards,</div><div class="gmail_extra"><br clear="all"><div><div dir="ltr"><span style="font-family:arial,sans-serif">
<p style="margin:0px;font-size:13px;border-collapse:collapse"><span style="color:rgb(0,0,0);text-transform:none;text-indent:0px;letter-spacing:normal;word-spacing:0px;white-space:normal;border-collapse:separate;font-size-adjust:none;font-stretch:normal"><span style="font-family:Helvetica"><span style="font-family:Calibri;font-size:12px"></span></span></span></p>
<div><font face="Arial"><span style="font-family:arial,sans-serif">
<p style="margin:0px;font-size:13px;border-collapse:collapse"><span lang="EN-US" style="font-family:Calibri">Werner Keil </span><span style="font-family:arial,sans-serif"><font face="Arial"><span style="font-family:arial,sans-serif"><span lang="EN-US" style="font-family:Calibri">| <font face="Arial"><span style="color:rgb(0,0,0);text-transform:none;text-indent:0px;letter-spacing:normal;word-spacing:0px;white-space:normal;border-collapse:separate;font-size-adjust:none;font-stretch:normal"><span style="font-family:arial,sans-serif;font-size:13px;border-collapse:collapse"><span lang="EN-US" style="font-family:Calibri">JCP Executive Committee Member, JSR 363 Co Spec Lead | Eclipse </span></span></span></font></span><span style="font-family:arial,sans-serif"><font face="Arial"><span style="font-family:arial,sans-serif"><span lang="EN-US" style="font-family:Calibri"><font face="Arial"><span style="color:rgb(0,0,0);text-transform:none;text-indent:0px;letter-spacing:normal;word-spacing:0px;white-space:normal;border-collapse:separate;font-size-adjust:none;font-stretch:normal"><span style="font-family:arial,sans-serif;font-size:13px;border-collapse:collapse"><span lang="EN-US" style="font-family:Calibri">UOMo Lead, Babel Language Champion</span></span></span></font></span></span></font></span></span></font></span><span style="font-family:Calibri"> </span><span style="font-family:Calibri">| Apache Committer</span></p>
</span></font><font face="Arial"><span style="font-family:arial,sans-serif">
<p style="margin:0px;font-size:13px;border-collapse:collapse"><span style="font-family:arial,sans-serif"><font face="Arial"><span style="font-family:arial,sans-serif"><span style="font-family:Helvetica;font-size:medium;border-collapse:separate"><span style="font-family:Calibri;font-size:12px">Twitter @wernerkeil </span></span><span style="font-family:arial,sans-serif"><font face="Arial"><span style="font-family:arial,sans-serif"><span style="font-family:Helvetica;font-size:medium;border-collapse:separate"><span style="font-family:Calibri;font-size:12px"><span style="font-size:13px;border-collapse:collapse"></span>|</span></span></span></font></span></span></font></span><span style="font-family:Helvetica;font-size:medium;border-collapse:separate"><span style="font-family:Calibri;font-size:12px"><span style="font-size:13px;border-collapse:collapse"></span> @UnitAPI | @JSR354 | </span><span style="font-family:Calibri;font-size:12px">#EclipseUOMo | </span></span><span style="font-family:Calibri;font-size:12px">#Java_Social | #DevOps</span></p>
</span></font></div></span><span lang="EN-GB">
<div style="font-family:arial,helvetica,sans-serif"><span style="font-family:arial,sans-serif"><font face="Arial"><span style="font-family:arial,sans-serif"><span style="font-family:Helvetica;font-size:medium;border-collapse:separate"><span style="font-family:Calibri;font-size:12px">Skype </span><span style="font-family:Calibri;font-size:12px"><span style="font-size:13px;border-collapse:collapse">werner.keil | Google+ <a href="http://gplus.to/wernerkeil" target="_blank">gplus.to/wernerkeil</a><br>
</span></span></span></span></font></span></div><div><div style="font-family:arial,sans-serif"><br></div><div><span style="font-family:arial">* Developer Week: 14/15 Jul 2014, Nürnberg, Germany. Werner Keil, JCP EC Member, JSR 363 Spec Lead, DevOps Guy will p</span>resent "Triple-E' class Continuous Delivery"<span style="font-family:arial,helvetica,sans-serif">, "JSR 363 and IoT"</span><font face="arial, helvetica, sans-serif"> (GER)</font><br>
</div><div><font face="arial, helvetica, sans-serif"><br></font></div><div><span style="font-size:small;font-family:arial">* JavaZone 2014: 9-11 Sep 2014, Oslo, Norway. Werner Keil, JCP EC Member, JSR 363 Spec Lead will p</span><font style="font-size:small">resent </font><span style="font-size:small;font-family:arial,helvetica,sans-serif">"JSR 363 - The Answer to Life Science and the Internet of Everything"</span><br>
</div><div><font face="arial, helvetica, sans-serif"><br></font></div><div><span style="font-family:arial,helvetica,sans-serif">* JavaOne 2014: Sep 28-Oct 2 2014, San Francisco, USA, Werner Keil, JCP EC Member, JSR 354 EG Member will host "Java and Digital Currencies, Friend or FOE"</span><font face="arial, helvetica, sans-serif"><br>
</font></div><div><font face="arial, helvetica, sans-serif"><br></font></div><div><span style="font-family:arial;font-size:small">* JMaghreb 3.0: 4-6 Nov 2014, Casablanca, Morocco. Werner Keil, JCP EC Member, JSR 363 Spec Lead, DevOps Guy will p</span><font style="font-size:small">resent "</font><font style="font-size:small">Triple-E' class DevOps"</font><span style="font-size:small;font-family:arial,helvetica,sans-serif">, "JSR 363"</span><font face="arial, helvetica, sans-serif"><br>
<br></font>* Mobile Developer Conference kompakt: 18 Nov 2014, Hamburg, Germany. Werner Keil, JCP EC Member, Apache DeviceMap Committer will present "<font color="#000000" face="Verdana" style="font-family:arial,sans-serif"><span style="font-size:12px">Apache DeviceMap</span></font>" (GER)</div>
</div></span></div></div>
<br><br><div class="gmail_quote">On Wed, Jul 2, 2014 at 10:43 PM, Antoine Sabot-Durand <span dir="ltr"><<a href="mailto:antoine@sabot-durand.net" target="_blank">antoine@sabot-durand.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi all,<br>
<br>
Since the first mention of CDI 2.0 preparation work, we've received a lot of comment about JSR 330 evolution. With the release of the proposal draft yesterday, this topic came up again. So let me give my point of view on this subject to have an open discussion here.<br>
<br>
When we started to discuss about modularity with Pete in last november, my first idea was to go see what we could add in JSR 330 to make it a true specification that could be the first module of CDI. My idea at that time was to discuss with JSR 330 owner to see if we could bring basic concept we have in CDI to AtInject spec. In my mind the main features would have been:<br>
- Enhance the javax.inject.Provider<T> interface to bring it at the same level than javax.enterprise.inject.Instance<T>. That would have included support for AnnotationLiteral and TypeLiteral as well<br>
- Add a Container interface (a very light BeanManger) in JSR 330 to be able to resolve beans instance from outside managed beans<br>
- Add a mechanism to get this Container from non managed beans (like we get access to BeanManager from JNDI or CDI class)<br>
<br>
At that time, I contacted Bob Lee without success (didn’t tried Pivotal since I don’t have contact there). I checked with JCP what could be done if we’d like to see an evolution of JSR 330 and the owner doesn’t care, there seems to have solutions but I let it aside since we were in the middle of CDI 1.2 MR at that time.<br>
<br>
Today I’m a bit torn about this point. Working on opening JSR 330 could be like opening pandora box, since I see 2 scenarios :<br>
<br>
1) former JSR 330 owners wake up and are ok to get for a new spec version they lead:<br>
Knowing the history of JSR 330 vs JSR 299 I’m not sure everything we’d need would be heard and even if the people leading this would be cooperative, a lot of discussion and negotiation would be needed to be sure that this new AtInject wouldn’t contain features incompatible with CDI. So it’d be very time consuming with no guarantee to get what we’d need at the end.<br>
<br>
2) former JSR 330 owner don’t mind others take ownership of their spec to enhance it and we (Red Hat) are the one to take this ownership to secure CDI:<br>
The best solution to minimize risk. But leading a new specification is a lot more work than just deciding that we have a specific basic inject « part » in CDI 2.0. Leading a spec is very time consuming, so it could be better on the paper but will impact CDI 2.0 new features.<br>
<br>
To sum up, as a Java EE user (like I have been for 10 years) I’d be happy to see this (scenario 2), but as CDI spec lead I fear that it could lead us in a trap (going to scenario 1 or consuming precious time on AtInject+1 instead of CDI 2.0)<br>
<br>
Your input, solutions or comment would be appreciated on this point.<br>
<span class="HOEnZb"><font color="#888888"><br>
Antoine<br>
<br>
<br>
</font></span></blockquote></div><br></div></div>