Description
Please direct comments on this JSR to the Spec Lead(s).
Stage timeline
| Stage | Access | Start | Finish |
|---|---|---|---|
| Final Release 3 | Download page | 22 Sep, 2006 | |
| Maintenance Draft Review 2 | Download page | 25 Jul, 2006 | 28 Aug, 2006 |
| Final Release 2 | Download page | 09 Feb, 2005 | |
| Maintenance Draft Review | Download page | 19 Nov, 2004 | 20 Dec, 2004 |
| Final Release | Download page | 25 Mar, 2003 | |
| Final Approval Ballot | View results | 04 Mar, 2003 | 17 Mar, 2003 |
| Proposed Final Draft | Download page | 26 Nov, 2002 | |
| Public Review | Download page | 31 Jul, 2002 | 29 Sep, 2002 |
| Community Draft Ballot | View results | 05 Mar, 2002 | 11 Mar, 2002 |
| Community Review | Login page | 04 Feb, 2002 | 11 Mar, 2002 |
| Expert Group Formation | 03 Apr, 2001 | 06 Jun, 2001 | |
| JSR Review Ballot | View results | 20 Mar, 2001 | 02 Apr, 2001 |
Team
Specification Leads
- Graham C TurrellIBM
Expert Group
- America Online (AOL)
- Cisco Systems
- Developmentor
- Fujitsu Limited
- IBM
- Novell, Inc.
- Oracle
- Progress Software
- Sun Microsystems, Inc.
- Systinet
Proposal
Identification |
Request |
Contributions
Original Summary: This JSR is to provide a standard set of APIs for representing and manipulating services described by WSDL (Web Services Description Language) documents.
These APIs will define a way to construct and manipulate models of service descriptions.
Section 1. Identification
Submitting Member: IBM Corporation
Name of Contact Person: Paul Fremantle
E-Mail Address: pzf@uk.ibm.com
FremantleTelephone Number: +44 1962 815 078
Fax Number: +44 1962 815 078
Specification Co-Lead: Paul Fremantle
E-Mail Address: pzf@uk.ibm.com
Telephone Number: +44 1962 815 078
Fax Number: +44 1962 815 078
Specification Co-Lead: Matthew Duftler
E-Mail Address: duftler@us.ibm.com
Telephone Number: +1 914 784 6084
Fax Number: +1 914 784 6324
Initial Expert Group Membership:
(Please provide company
or organization names. Note that expert group members must have
signed the JSPA.)
IBM Corporation
Section 2: Request
2.1 Please describe the proposed Specification:
This JSR is to provide a standard set of APIs for representing and manipulating services described by WSDL (Web Services Description Language) documents. These APIs will define a way to construct and manipulate models of service descriptions. The service descriptions can be treated by a client in a uniform manner, regardless of the origin of the descriptions. That is, the descriptions can be built as a result of parsing a WSDL document, constructed programmatically by direct invocation of the APIs, built using information provided by a user via a command-line or graphical interface, or built using information retrieved from a network source.
2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)
Java 2 SDK, Standard Edition v. 1.3 and above
2.3 What need of the Java community will be addressed by the proposed specification?
This set of APIs will allow developers to build applications using web services without having to manipulate WSDL documents directly; the proposed specification would allow developers to work with a higher-level set of APIs.
2.4 Why isn't this need met by existing specifications?
The Java 2 SDK Standard Edition does not provide a standard set of APIs for representing and manipulating services described by WSDL documents.
2.5 Please give a short description of the underlying technology or technologies:
By design, this proposed specification depends on the WSDL specification. WSDL is an XML format for describing network services as a set of endpoints operating on messages containing either document-oriented or procedure-oriented information.
In addition, since the WSDL specification describes bindings to SOAP, HTTP GET/POST and MIME, this proposed specification is also dependent on those technologies.
2.6 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)
javax.wsdl
2.7 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?
No.
2.8 Are there any security issues that cannot be addressed by the current security model?
No.
2.9 Are there any internationalization or localization issues?
No.
2.10 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work?
No.
2.11 Please describe the anticipated schedule for the development of this specification.
We should have API documentation and a preliminary specification ready by 6/1/2001 (approximately 12 weeks).
Section 3: Contributions
3.1 Please list any existing documents, specifications, or implementations that describe the technology. Please include links to the documents if they are publicly available.
3.2 Explanation of how these items might be used as a starting point for the work.
The WSDL specification describes the WSDL language upon which this proposed specification is based.