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

JSR273

StageJSR Review Ballot

Ballot durationApr 12, 2005 to Apr 25, 2005

Votes

SE/EE

Apache Software Foundation

Apple Computer, Inc.

BEA Systems

Borland Software Corporation

Fujitsu Limited

Google Inc.

Hewlett-Packard

IBM

Intel Corp.

Lea, Doug

Nortel

Oracle

Progress Software

Red Hat

SAP SE

Sun Microsystems, Inc.

Vote Log

SE/EE

On 2005-04-25 IBM voted Yes with no comment.
------------------------------------------------------------------------------
On 2005-04-25 Borland Software Corporation voted Yes with no comment.
------------------------------------------------------------------------------
On 2005-04-25 Fujitsu Limited voted Yes with no comment.
------------------------------------------------------------------------------
On 2005-04-12 Sun Microsystems, Inc. voted Yes with no comment.
------------------------------------------------------------------------------
On 2005-04-15 Red Hat voted Yes with no comment.
------------------------------------------------------------------------------
On 2005-04-18 Progress Software voted Yes with no comment.
------------------------------------------------------------------------------
On 2005-04-20 Nortel voted Yes with no comment.
------------------------------------------------------------------------------
On 2005-04-25 Intel Corp. voted Yes with the following comment:
We think the JSR inadvertantly provides a confused message about the relationship between JSR 273 and JSR 198.  The two JSRs should be independent.  While developers may find both useful, the spec from JSR 273 itself should not depend on JSR 198 APIs.  Answers in the JSR that imply there is a dependence or that the JSR 273 EG will be using the JSR 198 APIs should be revised to indicate there is none and that there is no expectation of any overlap.  

Additionally ... This JSR provides some information on TCK licensing terms for Sun J2SE licensees and for Not-for-profits.  It provides no information at all about TCK licensing terms (for licensing the TCK separate from the RI) for commercial Independent Implementations (for implementers who do not license the J2SE from Sun).  Licensing the TCK is required for any compatible Independent Implementation.  In order to know whether to invest in creation of an Independent Implementation or whether to participate in an Expert Group, it is important to know the terms and conditions for licensing the required TCK.  Otherwise, there is no way to know ahead of time whether it will be possible to create a compatible Independent Implementation at all.  We think this JSR should be modified to provide at least some information.  Any information would be better than none.  Ideally, we encourage Spec Leads to provide a public draft version of a TCK license (for licensing the TCK without the RI) at JSR initiation (subject to change in good faith as the spec develops).   
------------------------------------------------------------------------------
On 2005-04-25 SAP SE voted Yes with the following comment:
This JSR proposal currently states that this "... API will allow ... rich interaction with the host IDE by leveraging the JSR-198 API in conjunction with the additions to the JavaBeans APIs". We believe that a Design-Time API for JavaBeans is an important innovation and fully support its introduction to the Java platform, but that this capability must also be available to native IDE plug-in APIs such as the Eclipse API. We thank the Spec Lead for the clarification that this is indeed an important goal of this JSR. This does not invalidate JSR 198's goal to create a cross-IDE plug-in API. However, we believe that the market has yet to ascertain the priority for such an API. It is important that JSR 273 will focus on creating a powerful Design-Time API for Java Beans only. Creating a cross-IDE plug-in API is a separate goal and outside the scope of JSR 273.
------------------------------------------------------------------------------
On 2005-04-23 Lea, Doug voted Yes with no comment.
------------------------------------------------------------------------------
On 2005-04-23 Google Inc. voted Yes with no comment.
------------------------------------------------------------------------------
On 2005-04-24 Oracle voted Yes with no comment.
------------------------------------------------------------------------------
On 2005-04-24 Apache Software Foundation voted Yes with no comment.
------------------------------------------------------------------------------
On 2005-04-25 BEA Systems voted Yes with no comment.
------------------------------------------------------------------------------