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 #150
Internationalization Service for J2EE
JSR Review Ballot
Ballot duration: 2001-09-25 to: 2001-10-08

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

Votes

SE/EE

Accenture

Apache Software Foundation

Apple Computer, Inc.

BEA Systems

Borland Software Corporation

Caldera Systems

Cisco Systems

Compaq Computer Corporation

Fujitsu Limited

Hewlett-Packard

IBM

Lea, Doug

Oracle

Progress Software

Sun Microsystems, Inc.

WebGain

Icon Legend
Yes
No
Abstain
Not voted

View Vote Log

SE/EE

On 2001-10-08 BEA Systems voted Abstain with the following comment:
BEA shares similar concerns with this JSR and JSR 149. Although recent communicatiuon from IBM has helped to alleviate some of our concerns, we would like to see that clarification entered into the charter of the expert group (since there are already sufficient YES votes). We also are concerned about the amount of information which may need to be passed across a remote invocation. We believe this is an important topic, but are not yet convinced this is the best approach.
------------------------------------------------------------------------------
On 2001-10-08 Apache Software Foundation voted Yes with no comment.
------------------------------------------------------------------------------
On 2001-10-08 Sun Microsystems, Inc. voted Yes with the following comment:
Sun votes YES but is concerned that this JSR may be
defining protocol conventions for passing locale information
which might be better handled by other standards bodies.
We would recommend that the spec lead works with groups
such as OMG to establish common conventions that can
also be used for communication between Java and non-Java
applications.

Note that while this JSR may add new independent APIs and 
may describe the use of standard protocols to transmit such
information, any changes or extensions to existing APIs (such
as Connectors or JDBC) must be handled by the JSR Expert Group
or Maintenance Lead for the existing API.  For Connectors and
JDBC, Sun as Maintenance Lead will be happy to work with the
JSR-150 spec lead to define appropriate extensions.
------------------------------------------------------------------------------
On 2001-10-08 Oracle voted Yes with no comment.
------------------------------------------------------------------------------
On 2001-10-08 Hewlett-Packard voted Yes with no comment.
------------------------------------------------------------------------------
On 2001-10-08 Progress Software voted Yes with no comment.
------------------------------------------------------------------------------
On 2001-10-05 Fujitsu Limited voted Yes with the following comment:
We request that if this propagating function in the localization information has added to J2EE, the exsisting application should not effect on this change. The exsisting application should not required to update for this change.
------------------------------------------------------------------------------
On 2001-10-05 Compaq Computer Corporation voted Yes with no comment.
------------------------------------------------------------------------------
On 2001-10-05 Lea, Doug voted Abstain with the following comment:
I would also support Borland's suggestion that this
JSR be merged with JSR-149, but think that simply 
ensuring that EG members overlap would suffice.

I abstain from voting so that people who have
stronger opinions about which approach is more
workable can decide.
------------------------------------------------------------------------------
On 2001-10-04 Borland Software Corporation voted No with the following comment:
We believe that this JSR can be rolled in JSR 149 as a convention/example.  We think it makes sense to have JSR 149 discuss Work Area
conventions, and perhaps even use Internationalization as an example to illustrate how Work Areas could be used to solve a particular problem.  This JSR potentially opens
the door for lots of other special case Work Areas, which  not very generally useful.
------------------------------------------------------------------------------
On 2001-10-03 Caldera Systems voted Yes with no comment.
------------------------------------------------------------------------------
On 2001-10-01 IBM voted Yes with no comment.
------------------------------------------------------------------------------