<div dir="ltr">Hi all,<div><br></div><div>With my strong Java EE background, sentences like "<span style="font-size:12.8000001907349px">IMO CDI lite should be targeted to Java SE</span>", hurt ;o)</div><div><br></div><div>I remember talking with the JAX-RS guys (Java EE), years ago (back in EE6), and their answer for not adopting CDI was "too heavy". Today, a JBoss project called JBoss Forge (Java SE) is "dumping" CDI from its internals because it's too slow (George, could you develop a bit more this topic?). What do these two projects have in common ? They just need a "light" dependency injection framework. I was talking to the Forge guys (I think it was Lincoln) and, basically, they just need @Inject, @Qualifier and @Produces (the missing one).</div><div><br></div><div>My question is : do we need a CDI Lite, or do we need a "fatter" @Inject (for both SE and EE) ? I think that if we manage to move producers (and disposers) to JSR 330, then CDI would do the rest, no need for a Ligther version.</div><div><br></div><div>WDYT ?</div><div><br></div><div>Antonio</div><div><br></div><div>PS : With Antoine we talked to Juergen (co-spec lead od 330) and Patrick Curran (JCP Chair man) and it looks like another lead could take over 330 (I'm imagining RedHat talking the Lead role on 330). Even a maintenance release would be doable</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Aug 28, 2015 at 11:35 AM, 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"><div dir="ltr">Hi guys,<div><br></div><div>CDI lite is one of the big feature we are expected to deliver for version 2.0. I think it's time to start discussing about its design.</div><div><br></div><div>The big picture is to provide a consistent subset of CDI that could be implemented like Dagger is (code generated with process annotation). This would allow using CDI in constrained environment like mobile or embedded devices.</div><div><br></div><div>IMO CDI lite should be targeted to Java SE (I don't think it would make sense for Java EE). So, from a specification perspective, we''l probably have to split core part in 2 and se part as well (gosh).<br></div><div><br></div><div>I'm not sure regarding API. today they only weight 72 KB, so creating a subset only for the sake of the weight doesn't make sense. the only reason would be to have something clearer for the end user. but that could be tricky.</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>Antoine </div></font></span></div>
<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" rel="noreferrer" 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" rel="noreferrer" 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></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>