The JSR-330 spec was originally owned by Bob Lee (Google) and Rod
Johnson (SpringSource, now VMware). When Bob left Google, Google
gave the spec to him. Neither Bob nor VMware seems to have any
interest in moving this spec forward in the JCP. Without their
cooperation, nothing can happen. We would be happy for them to give
the spec over to someone who has both the interest and resources to
move it forward.|
Yoon Kyung Koo wrote on 11/06/12 05:05:
Indeed @Inject is defined in JSR-330 and JSR-330 was
originally planned for Java SE platform.
Then do you know what happened about JSR-330 and Java SE 7 or
I think if JSR-330 will be included in future Java SE then
it'll be more easily acceptable for other JSRs to use the
@Inject rather than using somewhat domain specific new
Software Innovation Evangelist
I prefer @Inject, and please keep in mind, that
annotation may be used by CDI, and given Bob Lee is too busy
with his work at Square to drive any changes, everything in
the Dependency Injection space still moving at JCP happens
via CDI, e.g. DeltaSpike, but to use @Inject you do not
depend the full CDI, only a handful of annotations that are
We are having this discussion in the Agorava Project, and
already have plans for Desktop/RCP or Mobile profiles or
Agorava where CDI may be replaced by something else like
Guice, etc. Same challenge here, but I would prefer to use
330/@Inject where it makes sense over a fragmentation and
forking of such annotations.
Keil | JCP Executive
Committee Member | Eclipse UOMo Lead | Java Godfather
Twitter @wernerkeil | #Java_Social | #EclipseUOMo
* DevoXX: November 13 2012, Antwerp,
Belgium. Werner Keil, JCP EC Member and Agorava
Committer, will present "Java Social JSR, it's alive"
DemoCamp: November 21 2012, Copenhagen, Denmark.
Werner Keil, Eclipse UOMo Lead and Mærsk Build Manager
will present "Eclipse M2M and
Standards for the IoT"
DemoCamp: November 26 2012, Berlin, Germany. Werner
Keil, Eclipse UOMo Lead and Mærsk Build Manager will
present "Eclipse M2M and
Standards for the IoT"
Eclipse DemoCamp: November 30 2012, Vienna, Austria.
Werner Keil, Eclipse
UOMo Lead and Mærsk Build Manager will present "Triple-E
class Continuous Delivery with Hudson, Maven, Kokki and
On Tue, Nov 6, 2012 at 10:02 AM,
Florent BENOIT <Florent.Benoit@...>
agree with Antonio, it easier for people that want to
inject something to always use @Inject instead of trying
to remember which annotation needs to be used for each
For using some specs outside of Java EE, they can
still use the dependency on CDI.
On Tue, Nov 6, 2012 at
9:53 AM, Antonio Goncalves <antonio.goncalves@...>
I am the opposite of Markus on this one.
I don't what to ask myself too
many questions : need to inject a
persistence context ? @Inject PersistenceContext.
Need to inject an EJB ?
@Inject MyEJB... and so on.
I'm already disappointed to see @Context in
JAX-RS. The programming model
should be as easy as possible.
Then comes the "I don't want to depend on
CDI". This to me sounds a bit
strange. CDI 1.1 is
standardizing bootstrapping in Java SE, so
what's the issue ? If the Batch JSR
needs CDI outside EE
it just bootstraps CDI in Java
SE. Then, depending on CDI
only really means depending on another
external jar (piece of cake for Maven)
I would like to see less custom technical
annotations (let's use @Inject when we can)
and in favour of more business annotation
that developers can create (thanks to
Stereotypes and Qualifiers)