<div dir="ltr">Reading my emails upside down, just found the link : <a href="https://dl.dropboxusercontent.com/u/2898173/cdi-spec.html" target="_blank" style="font-size:12.8000001907349px">https://dl.dropboxusercontent.com/u/2898173/cdi-spec.html</a><div><br></div><div>Antonio</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Apr 16, 2015 at 9:25 AM, Antonio Goncalves <span dir="ltr"><<a href="mailto:antonio.goncalves@gmail.com" target="_blank">antonio.goncalves@gmail.com</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">Antoine, I've lost track of this topic. Is the document somewhere ? Can we easily see the diffs ? <div><br></div><div>Managed Beans are already confusing.... turning it to "bean" can be even more confusing.</div><div><br></div><div>Antonio</div></div><div class="gmail_extra"><div><div class="h5"><br><div class="gmail_quote">On Wed, Apr 15, 2015 at 5:08 PM, Pete Muir <span dir="ltr"><<a href="mailto:pmuir@redhat.com" target="_blank">pmuir@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span><br>
> On 15 Apr 2015, at 13:31, Antoine Sabot-Durand <<a href="mailto:antoine@sabot-durand.net" target="_blank">antoine@sabot-durand.net</a>> wrote:<br>
><br>
> Hi all,<br>
><br>
> Rethinking of this task and reading the feedback on this, I really think we should go step by step on this splitting.<br>
><br>
> What I have produced here is a full extraction of EJB in the spec to put it in EE part.<br>
<br>
</span>Yes, this is a great start.<br>
<span><br>
> There are still Java EE references in core with EL, JSF, Servlet.<br>
<br>
</span>I’m least worried about EL, most about JSF and Serlet.<br>
<span><br>
><br>
> The more problematic part is the Contexts chapter: hard to remove servlet ref without rewriting all...<br>
><br>
> And yes, I did some rewording that could be no very nice.<br>
><br>
> In some places I replaces "Managed Beans or Session Beans" by the generic term "bean”.<br>
<br>
</span>This is definitely not ok, as you expanded the scope of the sentence to include built-in beans, producer methods, producer fields, and custom beans. I would suggest providing list of these changes, so we can review each one.<br>
<span><br>
> Java EE component was replaced by component (yes, I'm not sure it is very meaningful)<br>
<br>
</span>I also think this is problematic. A Java EE component is a specific thing. I would suggest providing list of these changes, so we can review each one.<br>
<span><br>
><br>
> In the EE part, I added changed all "session bean" occurrences by "EJB session bean”.<br>
<br>
</span>Ok, I don’t think this is a problem.<br>
<span><br>
><br>
> The step I see are:<br>
><br>
> 0) Validate that we're all ok with the principle of splitting<br>
> 1) validate that all EJB references are removed from core<br>
> 2) Correct bad terminology that I introduced<br>
><br>
> And then we should continue the splitting by rewriting the contexts chapter and EL references in Core.<br>
<br>
</span>+1<br>
<br>
><br>
> Antoine<br>
> _______________________________________________<br>
> cdi-dev mailing list<br>
> <a href="mailto:cdi-dev@lists.jboss.org" target="_blank">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>
<br>
_______________________________________________<br>
cdi-dev mailing list<br>
<a href="mailto:cdi-dev@lists.jboss.org" target="_blank">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></div></div><span class="HOEnZb"><font color="#888888">-- <br><div><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>
</font></span></div>
</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>