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 #346
Contexts and Dependency Injection for Java^TM EE 1.1
JSR Review Ballot
Ballot duration: 2011-04-12 to: 2011-04-25

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

Votes

SE/EE

Credit Suisse

Eclipse Foundation, Inc

Ericsson AB

Fujitsu Limited

Google Inc.

Hewlett-Packard

IBM

Intel Corp.

Keil, Werner

Oracle

Red Hat

SAP SE

VMware

Icon Legend
Yes
No
Abstain
Not voted

View Vote Log

SE/EE

On 2011-04-14 Intel Corp. voted Yes with no comment.
------------------------------------------------------------------------------
On 2011-04-24 Eclipse Foundation, Inc voted Yes with no comment.
------------------------------------------------------------------------------
On 2011-04-25 Google Inc. voted Yes with no comment.
------------------------------------------------------------------------------
On 2011-04-14 SAP SE voted Yes with no comment.
------------------------------------------------------------------------------
On 2011-04-14 Red Hat voted Yes with no comment.
------------------------------------------------------------------------------
On 2011-04-18 Credit Suisse voted Yes with no comment.
------------------------------------------------------------------------------
On 2011-04-18 Hewlett-Packard voted Yes with no comment.
------------------------------------------------------------------------------
On 2011-04-18 Oracle voted Yes with no comment.
------------------------------------------------------------------------------
On 2011-04-25 Keil, Werner voted Yes with no comment.
------------------------------------------------------------------------------
On 2011-04-25 IBM voted Yes with the following comment:
The CDI 1.1 proposal includes a number of enhancements which are desirable, but some are more properly handled elsewhere.  Interceptors are not a CDI specific technology and ordering of them should be addressed outside the scope of CDI as part of a common platform ordering mechanism.  This should be handled by the Java EE EG, where other common platform definitions occur or as part of an update to the Interceptors specification.  Annotation scanning behavior control should also be a platform issue, not a CDI specific issue.  Inconsistencies here will just make it more difficult for developers to understand and write code.  Lastly, the portability issues identified in Java EE 6 between JSRs 330 and 299 need to be addressed.  This is going to require a new JSR for Dependency Injection for Java and cooperation across the EGs to coordinate the changes.  It is our opinion that getting previously defined function working well together takes precedence over adding new functionality.  If this is not addressed by Public Draft, we would be forced to vote no for this technology.

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 2011-04-25 Ericsson AB voted Yes with no comment.
------------------------------------------------------------------------------
On 2011-04-25 Fujitsu Limited voted Yes with no comment.
------------------------------------------------------------------------------