<div dir="ltr">BTW, looks like Bob Lee is active because I can see he is planned to be in the expert group of Java Platform Module System<div><br></div><div><a href="https://jcp.org/en/jsr/detail?id=376">https://jcp.org/en/jsr/detail?id=376</a><br></div><div><br></div><div>Antonio</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 17, 2014 at 2:57 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>
Just to give you a small feedback of my Devoxx week regarding CDI and CDI 2.0 (for the rest, what happens in Devoxx stays in Devoxx ;) )<br>
<br>
1) Great expectations:<br>
I’m not going to state the obvious, but end user and other specs are watching us and expect a lot from CDI 2.0 (the question of total EJB replacement came more than once)<br>
<br>
2) Antonin Stefanutti and myself delivered a very valuable content in our CDI advanced university. I don’t remember being so proud of a talk material I released before. I encourage you to give it an eye and use it if you want. you can watch it on Slideshare [1] or grab the source slides on Antonin’s Github repo [2]<br>
<br>
3) Other spec are really willing to have a better integration.<br>
I met JMS, Servlet, JSF and MVC spec leaders, they all are looking for a better integration with CDI and are ok to take CDI specific part related to their spec back in their spec (Servlet and JSF mostly). Working with them will bring a more consistent Java EE and will reduce extra code from the spec.<br>
<br>
4) After months of discussion I finally met Jurgen Hoeller (Spring Framework) and Christian Gruber (Dagger and Guice) and we all agreed on a new version or MR of AtInject spec. Juergen will probably be the spec lead and we hope to have the big work done before mid 2015 (cross finger) to met our various agenda. That will probably add extra work for CDI 2.0 but will bring clarity and a good signal to the community. Thanks to Antonio who helped me on this.<br>
For those who remember the history of JSR 330 and JSR 299 the following picture will be nearly an historical one ;) [3]<br>
<br>
<br>
Antoine<br>
<br>
[1] <a href="http://www.slideshare.net/antoinesd/going-further-with-cdi-41411812" target="_blank">http://www.slideshare.net/antoinesd/going-further-with-cdi-41411812</a><br>
[2] <a href="https://github.com/astefanutti/further-cdi" target="_blank">https://github.com/astefanutti/further-cdi</a><br>
[3] <a href="http://twitter.com/antoine_sd/status/533710069255667712/photo/1" target="_blank">http://twitter.com/antoine_sd/status/533710069255667712/photo/1</a><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.</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr">Antonio Goncalves <br>Software architect, Java Champion and Pluralsight author<br><br><a href="http://www.antoniogoncalves.org" target="_blank">Web site</a> | <a href="http://twitter.com/agoncal" target="_blank">Twitter</a> | <a href="http://www.linkedin.com/in/agoncal" target="_blank">LinkedIn</a> | <a href="http://pluralsight.com/training/Authors/Details/antonio-goncalves" target="_blank">Pluralsight</a> | <a href="http://www.parisjug.org" target="_blank">Paris JUG</a> | <a href="http://www.devoxx.fr" target="_blank">Devoxx France</a></div></div>
</div>