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 #109
Implementing Enterprise Web Services
JSR Review Ballot
Ballot duration: 2001-03-06 to: 2001-03-19

These are the final results of the JSR Review Ballot for JSR #109. 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-03-19 BEA Systems voted Yes with the following comment:
BEA is cautiously voting yes, cautious because 
 (1) We agree with Sun that the Web Services bindings to Java eventually belong under the J2EE 1.4 umbrella, but we believe that JSR 109 should allow them to be so incorporated.  
 (2) We remain concerned that the scope of this JSR is overly broad. BEA believes what the Java market most urgently needs is a minimal solution for binding SOAP, UDDI, & WSDL. Minimal in these sense that we envision these to be application-invisible wrappers (using deployment descriptors & minimal APIs additions) around stateless session beans and Mbeans. Standardization for ebXML and other higher level Web Services will require more work, so we remain worred that defining an overarching "runtime and programming model that consistently encompasses services" will distract us from ensuring that simple Web Services are indeed handled minimally and in a timely fashion.
------------------------------------------------------------------------------
On 2001-03-19 WebGain voted Yes with no comment.
------------------------------------------------------------------------------
On 2001-03-19 Sun Microsystems, Inc. voted No with the following comment:
Sun supports the goal of standardizing the J2EE app model for implementing a web service. In fact, customer requirements gathered from licensees indicate a J2EE web services app model is a critical requirement for J2EE 1.4.

This JSR states it will define a 'programming model and architecture for implementing web services in Java. It is not clear how this work is intended to be scoped nor how it is to be made part of J2EE.
 
This JSR needs to define more precisely either what it is going to produce or what specific problem it solves.  Also, this JSR needs to
include a requirement that all work done by it should be explicitly engineered to become a J2EE requirement.
 
We recommend that J2EE web service support be defined directly by the J2EE 1.4 Platform JSR since this support involves primarily the addition
of new J2EE container requirements rather than new J2EE APIs.
 
If this JSR is accepted, its work must be closely coordinated with the J2EE 1.4 Platform JSR. 
------------------------------------------------------------------------------
On 2001-03-19 Borland Software Corporation voted Yes with no comment.
------------------------------------------------------------------------------
On 2001-03-19 Progress Software voted Yes with no comment.
------------------------------------------------------------------------------
On 2001-03-19 Hewlett-Packard voted Yes with no comment.
------------------------------------------------------------------------------
On 2001-03-19 Compaq Computer Corporation voted Yes with no comment.
------------------------------------------------------------------------------
On 2001-03-18 Lea, Doug voted No with the following comment:
This JSR seems to cover important issues.
But the goals and scope of the JSR are not clearly explained. I can't in good conscience vote for a proposal
that I may later vote against accepting because it turned out to
address issues, APIs etc that I didn't expect.

I think it would have been logistically better to first ask other
vendors to help enumerate this list of decisions etc (also asking for
them to become initial expert group members). Without more precision
at least on problem-statements, I don't have a clear sense of what
this JSR will produce, or how to later evaluate its success.
------------------------------------------------------------------------------
On 2001-03-08 IBM voted Yes with no comment.
------------------------------------------------------------------------------
On 2001-03-06 Cisco Systems voted Yes with no comment.
------------------------------------------------------------------------------