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 #299
Contexts and Dependency Injection for the Java^TM EE platform
Final Approval Ballot
Ballot duration: 2009-11-17 to: 2009-11-30

These are the final results of the Final Approval Ballot for JSR #299. 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

Oracle

Peierls, Tim

Red Hat

SAP SE

Sun Microsystems, Inc.

VMware

Icon Legend
Yes
No
Abstain
Not voted

View Vote Log

SE/EE

On 2009-11-19 Google Inc. voted Yes with no comment.
------------------------------------------------------------------------------
On 2009-11-24 Keil, Werner voted Yes with no comment.
------------------------------------------------------------------------------
On 2009-11-18 Red Hat voted Yes with no comment.
------------------------------------------------------------------------------
On 2009-11-30 SAP SE voted Yes with no comment.
------------------------------------------------------------------------------
On 2009-11-30 Fujitsu Limited voted Yes with no comment.
------------------------------------------------------------------------------
On 2009-11-30 Apache Software Foundation voted Yes with the following comment:
We appreciate the use of the Apache License for the RI and TCK. We believe that access to TCKs with no market, distribution of functionality restrictions is an important vehicle for ensuring compatible independent implementations of Java specifications.
------------------------------------------------------------------------------
On 2009-11-29 Intel Corp. voted Yes with the following comment:
The TCK for this JSR is made available under the Apache License so there are no issues related to the following general comment.

This is a general comment we make in each ballot  By the agreement that forms the JCP, other than reciprocity rules for licensing and three compatibility conditions (including passing the TCK test suite) "the Spec Lead agrees not to impose any contractual condition or covenant that would limit or restrict the right of any licensee to create or distribute such Independent Implementations." The Apache Foundation claims in an open letter that they have been unable to obtain a TCK License that does not restrict compatible implementations of the SE Platform (additional restrictions that are not in the  specification itself). 
------------------------------------------------------------------------------
On 2009-11-20 Ericsson AB voted Yes with no comment.
------------------------------------------------------------------------------
On 2009-11-21 Peierls, Tim voted Yes with no comment.
------------------------------------------------------------------------------
On 2009-11-30 Hewlett-Packard voted Yes with no comment.
------------------------------------------------------------------------------
On 2009-11-18 Oracle voted Yes with no comment.
------------------------------------------------------------------------------
On 2009-11-17 Sun Microsystems, Inc. voted Yes with no comment.
------------------------------------------------------------------------------
On 2009-11-30 IBM voted No with the following comment:
The current lack of portability between JSR 330 and JSR 299 applications will create significant difficulties for the community. Application developers who use patterns based on JSR 330 injection annotations and proprietary injection mechanisms will experience integration issues when taking advantage of JSR 299 contexts associated with JSF. Insufficient attention has been paid to these details in the development of these specifications and this will reflect poorly on the Java EE platform as a whole. Although IBM previously voted in support  of both JSR 299 and 330 with the clear expectation that the "SE/EE injection programming model must be aligned into a single extensible programming model that defines a core set of functionality for SE and extends that with EE functionality", this has not yet been achieved. IBM will continue to support both expert groups in the development of a single integrated and extensible injection programming model. 

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-11-30 Lea, Doug voted Yes with no comment.
------------------------------------------------------------------------------