Printed: Sep 26, 2024
From: http://jcp.org/en/jsr/detail?id=93
|
Specification Leads | |||
Paul Sterk | Sun Microsystems, Inc. | ||
Expert Group | |||
BEA Systems | Cisco Systems | Electronic Data Systems (EDS) | |
Encoda Systems, Inc. | Extol, Inc. | Hewlett-Packard | |
IBM | Kim, Chaemee | Novell, Inc. | |
NTT (Nippon Telegraph & Telephone) Corporation | Progress Software | Sterling Commerce | |
Sun Microsystems, Inc. | Sybase | Vitria Technology | |
WebGain | WebMethods Corporation |
Original Java Specification Request (JSR)
Identification |
Request |
Contributions
Section 1. Identification
Submitting Member: Sun Microsystems, Inc.
Name of Contact Person: Farrukh Najmi
E-Mail Address: najmi@east.sun.com
Telephone Number: (781) 442-0703
Fax Number: (781) 442-1610
Specification Lead: Farrukh Najmi
E-Mail Address: najmi@east.sun.com
Telephone Number: (781) 442-0703
Fax Number: (781) 442-1610
Initial Expert Group Membership:
(Please provide company or organization names. Note that expert group
members must have signed the JSPA.)
Cisco Systems
Vitria
XML Solutions
Nippon Telegraph and Telephone (NTT) Corporation
webMethods Inc.
Section 2: Request
This specification will describe Java API's designed specifically for an open and interoperable set of registry services that enable sharing of information between interested parties. The shared information is maintained as objects in a compliant registry. All access to registry content is exposed via the interfaces defined for the Registry Services.
Currently there are numerous open standards for distributed registries. Examples include OASIS, eCo Framework, ebXML. In addition there also exists industry consortium led efforts such as UDDI which may eventually be donated to a standard body. JAXR will provide a uniform and standard API for accessing information from these registries within the Java platform.
It is planned that this JSR will leverage work currently under way in the ebXML Registry Working Group, Oasis, ISO, W3C, IETF and potentially other relevant open standardsbodies.
This JSR does not aim to define either business Registry standards, XML messaging standards or XML schemas for particular tasks. These standards belong in standards bodies such as OASIS or IETF. Instead this JSR aims to define standard Java APIs to allow convenient access from Java to emerging open Registry standards, such as the ebXML Registry standard.
The JAXR 1.0 specification will be provided initially as an optional package, but may be incorporated into the Java 2 Enterprise Edition platform as soon as this is practical and there is sufficient demand to warrant such integration.
JAXR 1.0 will specify API's enabling the Java Community to develop portable eBusiness applications and tools that support emerging industry standards for XML registries on the internet. Among candidate capabilities are:
Existing specification such as JNDI are not suitable for meeting the requirements of business registries as outlined in section 2.3.
Given the diversity of communication requirements and technologies amongst multiple trading partners, there is currently no standard way to accomplish the sharing of business content between trading partners, using public or private registries. However, industry standards are emerging.
More specifically, there is currently no standard Java API facilitating the use of the many registries that are becoming available over the web. The ability to describe a standard way to access content in these registries will facilitate dynamic discovery of business partners and services and subsequently enable Web based business-to-business communication.
Although this specification will focus exclusively on business applications written using the Java platform with messages and services described using XML (as specified by open industry standards such as ebXML), such applications will be capable of interoperating with all applications conforming to a common message exchange schema.
The JAXR 1.0 specification will specify abstract Java interfaces specifically targeted to provide a simple to use Java API for accessing internet registries. The specifications will be developed by industry experts to ensure that JAXR clients can access business registries based on open standards such as ebXML, OASIS, eCo framework as well as other industry consortium led registry specifications such as UDDI.
In addition, the JAXR specification assumes that all communication between registry and registry clients will be based on the Java API for XML Messaging (JAXM) specification.
javax.xml.registry
No
No. The goal is to leverage the security services of the Java TM2 platform, Standard Edition and Java 2 platform, Enterprise Edition where possible.
No. The goal is to leverage the I18N services of the Java 2 platform, Standard Edition. There are no localization implications at this time.
None
Community Draft Q1 2001
Public Draft Q2 2001
Section 3: Contributions
The Java API for XML Messaging 1.0 defines how XML messages are exchanged between a registry client and a registry implementation. This specification is key to ensuring interoperable communication between any ebXML registry client and any ebXML Registry implementation.
The ebXML Registry Information Model Specification v0.3 provides the information model that: