The Java Community Process(SM) Program - JSRs: Java Specification Requests

Use of JCP site is subject to the JCP Terms of Use and the Oracle Privacy Policy

JSR #330
Dependency Injection for Java
Final Approval Ballot
Ballot duration: 2009-09-29 to: 2009-10-12

These are the final results of the Final Approval Ballot for JSR #330. The Executive Committee for SE/EE has approved this ballot.

Votes

SE/EE

Apache Software Foundation

Eclipse Foundation, Inc

Ericsson AB

Fujitsu Limited

Google Inc.

Hewlett-Packard

IBM

Intel Corp.

Keil, Werner

Lea, Doug

Nortel

Oracle

Red Hat

SAP SE

Sun Microsystems, Inc.

VMware

Icon Legend
Yes
No
Abstain
Not voted

View Vote Log

SE/EE

On 2009-10-12 Fujitsu Limited voted Yes with no comment.
------------------------------------------------------------------------------
On 2009-09-30 Intel Corp. voted Yes with the following comment:
Incredible job by the Expert Group in moving this JSR to completion in just 4 months!  It shows the standards process doesn't have to be slow when there is agreement on how to proceed.

Also, JSR 330 making the TCK available under an open source license ensures there are no inappropriate restrictions on spec implementations imposed by the test suite license.
------------------------------------------------------------------------------
On 2009-10-09 Sun Microsystems, Inc. voted Yes with the following comment:
We are grateful to the specification leads and the entire expert group for bringing this specification to completion in a very short time frame, so as to accommodate the needs of the Java EE 6 platform. In order to maintain a consistent programming model for dependency injection throughout the Java platform, it is vital that the expert groups for any future revisions of JSR-330 and JSR-299 continue to cooperate closely.
------------------------------------------------------------------------------
On 2009-10-01 Lea, Doug voted Yes with no comment.
------------------------------------------------------------------------------
On 2009-10-08 Keil, Werner voted Yes with no comment.
------------------------------------------------------------------------------
On 2009-10-09 Hewlett-Packard voted Yes with no comment.
------------------------------------------------------------------------------
On 2009-10-06 Eclipse Foundation, Inc voted Yes with no comment.
------------------------------------------------------------------------------
On 2009-10-06 VMware voted Yes with no comment.
------------------------------------------------------------------------------
On 2009-10-11 Red Hat voted Yes with the following comment:
We are proceeding in good faith that the 330 group will treat 299 as an important customer going forward despite minor last minute differences.  In order to maintain a consistent programming model for dependency injection throughout the Java platform, it is vital that the expert groups for any future revisions of JSR-330 and JSR-299 continue to cooperate closely.
------------------------------------------------------------------------------
On 2009-10-02 Apache Software Foundation voted Yes with no comment.
------------------------------------------------------------------------------
On 2009-10-01 Ericsson AB voted Yes with no comment.
------------------------------------------------------------------------------
On 2009-10-12 IBM voted No with the following comment:
The original proposed goal of this JSR has not been met and that has
created programming model portability issues.  We have been supporters of
this proposal on the grounds that the "SE/EE injection programming model be
aligned into a single extensible programming model that defines a core set
of functionality for SE and extends that with EE functionality".  The
current state of JSRs 330 and 299 do not provide a single extensible
programming model.  JSR 330 did not cover the proposed type-safe injector
configuration API, nor were default binding rules defined in the absence of
a configuration API.  As as result, applications written for SE will
require a porting effort to run them in an EE environment.  Given that a
single extensible programming model has not been achieved, we cannot
support the standardization of two different injection models with
divergent and non-portable behaviors. We remain expectant that these
portability issues will be resolved through updates to JSR 330 and the
final version of JSR 299.

IBM's vote is based on the technical merits of this JSR and is not a vote
on the licensing terms.  IBM supports licensing models that create an open
and level playing field by allowing third parties to create independent
implementations of Java Specifications and that do not allow individuals or
companies to exercise unnecessary control for proprietary advantage.  We
support open source as a licensing model for contributions in the JCP, and
would hope others will support this direction. This comment is not
necessarily directed at the current business or license terms for this JSR,
however, it is a statement of IBM's preferred licensing model.
------------------------------------------------------------------------------
On 2009-10-12 SAP SE voted Yes with no comment.
------------------------------------------------------------------------------
On 2009-10-02 Oracle voted Yes with no comment.
------------------------------------------------------------------------------
On 2009-09-30 Google Inc. voted Yes with no comment.
------------------------------------------------------------------------------