Hi all,
With my strong Java EE background, sentences like "IMO CDI lite should be targeted to Java SE", hurt ;o)
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).
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.
WDYT ?
Antonio
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