@Antoine, so which content do you see in CDI Lite ? Are you sure about
events ?
I'm in favor of a "fatter" 330 that would have :
- @Inject : already there
- @Qualifier : already there
-
*Producers and disposers *
-
*Programatic lookup *
- *Java SE Bootstrap*
When you say "*The goal here is not to propose a new EE profile but a
subspec*", 330 could already be seen as a subspec. If you put events
apparts, what would be missing in this list in your point of view ? And
what obstacles do you see in archieving this ?
To boostrap CDI we have a CDIProvider, why not having an InjectionProvider
just to bootstrap 330 (then, CDIProvider could extend InjectionProvider, so
it bootstraps the all thing) ?
Antonio
On Sun, Aug 30, 2015 at 9:09 AM, Antoine Sabot-Durand <
antoine(a)sabot-durand.net> wrote:
Yes Arjan, I think it's the first reason. We really should work
with them
to understand what should be added to CDI 2.0 to have it as a first citizen
DI in their spec.
Le sam. 29 août 2015 à 23:15, arjan tijms <arjan.tijms(a)gmail.com> a
écrit :
> On Sat, Aug 29, 2015 at 8:45 PM, Antonio Goncalves
> <antonio.goncalves(a)gmail.com> wrote:
> > 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".
>
> I can't find an exact reference anymore, but I somewhat remember that
> one of the reasons was also simply that CDI as a general solution
> finished late in Java EE 6, while JAX-RS finished earlier and had all
> the work for their own DI solution already done.
>
--
Antonio Goncalves
Software architect, Java Champion and Pluralsight author
Web site <
http://www.antoniogoncalves.org> | Twitter
<
http://twitter.com/agoncal> | LinkedIn <
http://www.linkedin.com/in/agoncal>
|
Pluralsight
<
http://pluralsight.com/training/Authors/Details/antonio-goncalves> | Paris
JUG <
http://www.parisjug.org> | Devoxx France <
http://www.devoxx.fr>