<div dir="ltr">Antonio/all,<div><br></div><div>JSR 330 was never a "subspec" of CDI, but CDI simply extended it. Just like e.g. Portlet, JSP or JSF all extend and build around a standard like Servlets.</div><div><br></div><div>Antoine mentioned Dagger, so if a CDI "lite" aims at SE, would the minimum version also be SE 8 or could it be more widely usable, at least on the Spec/API side? </div><div><br></div><div>We all know, Android is a bit of a red hering for Oracle with all that lawsuit mess going on seemingly forever. Especially Dagger now that Google took ownership again with 2.0 also aims at Android among other SE environments. The minimum JVM version is Java SE 7 according to the POM. </div><div><br></div><div>If there's anything similar to a CDI lite as a subset, it's probably CLDC/Java ME. Compared to Java SE it has a much smaller footprint with even the same class often being reduced in its number of methods. Not sure, if the latter was really necessary for CDI lite, but reducing the number of overall API elements should help to get it small and useful enough for SE.<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></div></div></div></div></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On Sun, Aug 30, 2015 at 3:22 PM, <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" rel="noreferrer" 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. Re: Time to start working on CDI lite (Antoine Sabot-Durand)<br>
2. Re: Time to start working on CDI lite (Antoine Sabot-Durand)<br>
3. Re: Time to start working on CDI lite (Antonio Goncalves)<br>
4. Re: Time to start working on CDI lite (John D. Ament)<br>
<br><br>
------------------------------<br>
<br>
Message: 3<br>
Date: Sun, 30 Aug 2015 14:06:33 +0200<br>
From: Antonio Goncalves <<a href="mailto:antonio.goncalves@gmail.com">antonio.goncalves@gmail.com</a>><br>
Subject: Re: [cdi-dev] Time to start working on CDI lite<br>
To: Antoine Sabot-Durand <<a href="mailto:antoine@sabot-durand.net">antoine@sabot-durand.net</a>><br>
Cc: cdi-dev <<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a>><br>
Message-ID:<br>
<<a href="mailto:CA%2BZZq9-RW68R%2Bo1c3n5J6KSGtki%2Bo%2B89SvTpovSFL5ZKq6BTWQ@mail.gmail.com">CA+ZZq9-RW68R+o1c3n5J6KSGtki+o+89SvTpovSFL5ZKq6BTWQ@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
@Antoine, so which content do you see in CDI Lite ? Are you sure about<br>
events ?<br>
<br>
I'm in favor of a "fatter" 330 that would have :<br>
<br>
- @Inject : already there<br>
- @Qualifier : already there<br>
-<br>
*Producers and disposers *<br>
-<br>
*Programatic lookup *<br>
- *Java SE Bootstrap*<br>
<br>
When you say "*The goal here is not to propose a new EE profile but a<br>
subspec*", 330 could already be seen as a subspec. If you put events<br>
apparts, what would be missing in this list in your point of view ? And<br>
what obstacles do you see in archieving this ?<br>
<br>
To boostrap CDI we have a CDIProvider, why not having an InjectionProvider<br>
just to bootstrap 330 (then, CDIProvider could extend InjectionProvider, so<br>
it bootstraps the all thing) ?<br>
<br>
Antonio<br>
<br>
On Sun, Aug 30, 2015 at 9:09 AM, Antoine Sabot-Durand <<br>
<a href="mailto:antoine@sabot-durand.net">antoine@sabot-durand.net</a>> wrote:<br>
<br>
> Yes Arjan, I think it's the first reason. We really should work with them<br>
> to understand what should be added to CDI 2.0 to have it as a first citizen<br>
> DI in their spec.<br>
><br>
> Le sam. 29 ao?t 2015 ? 23:15, arjan tijms <<a href="mailto:arjan.tijms@gmail.com">arjan.tijms@gmail.com</a>> a<br>
> ?crit :<br>
><br>
>> On Sat, Aug 29, 2015 at 8:45 PM, Antonio Goncalves<br>
>> <<a href="mailto:antonio.goncalves@gmail.com">antonio.goncalves@gmail.com</a>> wrote:<br>
>> > I remember talking with the JAX-RS guys (Java EE), years ago (back in<br>
>> EE6),<br>
>> > and their answer for not adopting CDI was "too heavy".<br>
>><br>
>> I can't find an exact reference anymore, but I somewhat remember that<br>
>> one of the reasons was also simply that CDI as a general solution<br>
>> finished late in Java EE 6, while JAX-RS finished earlier and had all<br>
>> the work for their own DI solution already done.<br>
>><br>
><br>
<br>
<br>
--<br>
Antonio Goncalves<br>
Software architect, Java Champion and Pluralsight author<br>
<br>
Web site <<a href="http://www.antoniogoncalves.org" rel="noreferrer" target="_blank">http://www.antoniogoncalves.org</a>> | Twitter<br>
<<a href="http://twitter.com/agoncal" rel="noreferrer" target="_blank">http://twitter.com/agoncal</a>> | LinkedIn <<a href="http://www.linkedin.com/in/agoncal" rel="noreferrer" target="_blank">http://www.linkedin.com/in/agoncal</a>> |<br>
Pluralsight<br>
<<a href="http://pluralsight.com/training/Authors/Details/antonio-goncalves" rel="noreferrer" target="_blank">http://pluralsight.com/training/Authors/Details/antonio-goncalves</a>> | Paris<br>
JUG <<a href="http://www.parisjug.org" rel="noreferrer" target="_blank">http://www.parisjug.org</a>> | Devoxx France <<a href="http://www.devoxx.fr" rel="noreferrer" target="_blank">http://www.devoxx.fr</a>><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://lists.jboss.org/pipermail/cdi-dev/attachments/20150830/6d57ffc9/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.jboss.org/pipermail/cdi-dev/attachments/20150830/6d57ffc9/attachment-0001.html</a><br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Sun, 30 Aug 2015 13:22:04 +0000<br>
From: "John D. Ament" <<a href="mailto:john.d.ament@gmail.com">john.d.ament@gmail.com</a>><br>
Subject: Re: [cdi-dev] Time to start working on CDI lite<br>
To: Antonio Goncalves <<a href="mailto:antonio.goncalves@gmail.com">antonio.goncalves@gmail.com</a>>, Antoine<br>
Sabot-Durand <<a href="mailto:antoine@sabot-durand.net">antoine@sabot-durand.net</a>><br>
Cc: cdi-dev <<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a>><br>
Message-ID:<br>
<<a href="mailto:CAOqetn_Afc0BfGPcSRBQiKuvtOfZnQKzxHv59KhbJfLTGKoH4w@mail.gmail.com">CAOqetn_Afc0BfGPcSRBQiKuvtOfZnQKzxHv59KhbJfLTGKoH4w@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Personally, I'm not in favor of a slimmed down runtime. It was tried with<br>
EJB, but never implemented properly (most implementations that support<br>
EJB-lite actually support the entire thing, except for deprecated stuff).<br>
<br>
I think if we define SE properly we won't have a need for this.<br>
<br>
John<br>
<br>
On Sun, Aug 30, 2015 at 8:07 AM Antonio Goncalves <<br>
<a href="mailto:antonio.goncalves@gmail.com">antonio.goncalves@gmail.com</a>> wrote:<br>
<br>
> @Antoine, so which content do you see in CDI Lite ? Are you sure about<br>
> events ?<br>
><br>
> I'm in favor of a "fatter" 330 that would have :<br>
><br>
> - @Inject : already there<br>
> - @Qualifier : already there<br>
> -<br>
> *Producers and disposers *<br>
> -<br>
> *Programatic lookup *<br>
> - *Java SE Bootstrap*<br>
><br>
> When you say "*The goal here is not to propose a new EE profile but a<br>
> subspec*", 330 could already be seen as a subspec. If you put events<br>
> apparts, what would be missing in this list in your point of view ? And<br>
> what obstacles do you see in archieving this ?<br>
><br>
> To boostrap CDI we have a CDIProvider, why not having an InjectionProvider<br>
> just to bootstrap 330 (then, CDIProvider could extend InjectionProvider, so<br>
> it bootstraps the all thing) ?<br>
><br>
> Antonio<br>
><br>
> On Sun, Aug 30, 2015 at 9:09 AM, Antoine Sabot-Durand <<br>
> <a href="mailto:antoine@sabot-durand.net">antoine@sabot-durand.net</a>> wrote:<br>
><br>
>> Yes Arjan, I think it's the first reason. We really should work with them<br>
>> to understand what should be added to CDI 2.0 to have it as a first citizen<br>
>> DI in their spec.<br>
>><br>
>> Le sam. 29 ao?t 2015 ? 23:15, arjan tijms <<a href="mailto:arjan.tijms@gmail.com">arjan.tijms@gmail.com</a>> a<br>
>> ?crit :<br>
>><br>
>>> On Sat, Aug 29, 2015 at 8:45 PM, Antonio Goncalves<br>
>>> <<a href="mailto:antonio.goncalves@gmail.com">antonio.goncalves@gmail.com</a>> wrote:<br>
>>> > I remember talking with the JAX-RS guys (Java EE), years ago (back in<br>
>>> EE6),<br>
>>> > and their answer for not adopting CDI was "too heavy".<br>
>>><br>
>>> I can't find an exact reference anymore, but I somewhat remember that<br>
>>> one of the reasons was also simply that CDI as a general solution<br>
>>> finished late in Java EE 6, while JAX-RS finished earlier and had all<br>
>>> the work for their own DI solution already done.<br>
>>><br>
>><br>
><br>
><br>
> --<br>
> Antonio Goncalves<br>
> Software architect, Java Champion and Pluralsight author<br>
><br>
> Web site <<a href="http://www.antoniogoncalves.org" rel="noreferrer" target="_blank">http://www.antoniogoncalves.org</a>> | Twitter<br>
> <<a href="http://twitter.com/agoncal" rel="noreferrer" target="_blank">http://twitter.com/agoncal</a>> | LinkedIn<br>
> <<a href="http://www.linkedin.com/in/agoncal" rel="noreferrer" target="_blank">http://www.linkedin.com/in/agoncal</a>> | Pluralsight<br>
> <<a href="http://pluralsight.com/training/Authors/Details/antonio-goncalves" rel="noreferrer" target="_blank">http://pluralsight.com/training/Authors/Details/antonio-goncalves</a>> | Paris<br>
> JUG <<a href="http://www.parisjug.org" rel="noreferrer" target="_blank">http://www.parisjug.org</a>> | Devoxx France <<a href="http://www.devoxx.fr" rel="noreferrer" target="_blank">http://www.devoxx.fr</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" 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<br>
> code under the Apache License, Version 2 (<br>
> <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<br>
> provided on this list, the provider waives all patent and other<br>
> intellectual property rights inherent in such information.<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://lists.jboss.org/pipermail/cdi-dev/attachments/20150830/64394d4f/attachment.html" rel="noreferrer" target="_blank">http://lists.jboss.org/pipermail/cdi-dev/attachments/20150830/64394d4f/attachment.html</a><br>
<br>
------------------------------<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" 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>
<br>
End of cdi-dev Digest, Vol 57, Issue 31<br>
***************************************<br>
</blockquote></div><br></div></div></div>