[January 23, 2001] A Java Specification Request 'JSR-000093' from Sun proposes a Java API for XML Registries 1.0. JAXR "provides an API for a set of distributed Registry Services that enables business-to-business integration between business enterprises, using the protocols being defined by ebXML.org, OASIS, ISO 11179. 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. 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 goal is to leverage the security services of the Java platform, Standard Edition and Java 2 platform, Enterprise Edition where possible." Details: "This JSR requests the creation of the Java API for XML Registries 1.0 specification (JAXR). JAXR may be viewed as analogous to Java Naming and Directory Interface (JNDI) but designed specifically for internet sharing of XML-related business information. 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 standards bodies. 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: support for industry standard XML registry functionality, support for registration of member organizations and enterprises, support for submission and storing of arbitrary registry content, support for life cycle management of XML and non-XML registry content, support for user-defined associations between registry content, support for user-defined multi-level classification of registry content along multiple user defined facets, support for registry content querying based on defined classification schemes, support for registry content querying based on complex ad hoc queries, support for registry content querying based on keyword based search, support for sharing of web services, support for sharing of business process between partners, support for sharing of schemas between partners, support for sharing of business documents between partners support for trading partner agreement assembly and negotiation, support for schema assembly, support for heterogeneous distributed registries support for enabling publish/subscribe XML Messaging between parties..."
References:
Java API for XML Registries 1.0. Proposed Specification Lead: Farrukh Najmi (Sun Microsystems). Status: JSR Review Closes 2001.01.22. [cache]
See also: Java API for XML Messaging (JAXM). "This JSR requests the creation of the Java API's for XML Messaging 1.0 specification (JAXM). This specification will describe Java API's designed specifically for the exchange of XML business documents such as, invoices, purchase orders, and order confirmations. This JSR will refer to such documents generically as business messages or messages for short..." See (1) The M Project (Early Access Prototype) and (2) the specification currently under review by the Java Community Process (JSR-000067).
[December 18, 2002] "Publish and Find UDDI tModels with JAXR and WSDL." By Frank Sommers. In JavaWorld (December 13, 2002). ['This article presents a programming model for publishing and discovering Web services based on service interfaces. It starts by defining reusable WSDL (Web Services Description Language) interface documents and shows how to register those interfaces as UDDI (Universal Description, Discovery, and Integration) tModels using the Java API for XML Registries (JAXR). Then the article focuses on how Web service clients use well-known tModels to discover and invoke services that adhere to a set of interfaces.'] "... The pattern of finding all implementations of a Web service interface and possibly invoking those service instances proves useful in other contexts as well. Portal Websites still rely on manual -- or semi-manual -- compilation of news articles, automobile inventories, available hotel rooms, or airline seats. Even when data exchanges electronically, that automation often comes at the expense of lengthy and pricey system integration. Among the biggest motivations for building Web services is the desire to automate those tedious information-gathering tasks. This article provides a working example of how UDDI (Universal Description, Discovery, and Integration) registries, the Java API for XML Registries (JAXR), and the Web Services Description Language (WSDL) work together to initiate that automation. Currently, several industry groups are working to define Web service interface standards. Examples are the Open Travel Alliance for travel, the Star Consortium for automotive retail, and RosettaNet for supply chain management. Many of those groups employ a community-oriented process and make their specifications available to anyone for comments. Real-world interface specifications aim to be comprehensive and are rather complex. Thus, to make this article easy to follow, I use a simple interface definition for the example cruise ship destination Web service. That interface features only a single method. When invoked, that method produces a list of destinations a cruise company serves..."
See also: Java, Technology, and XML. "Java is ideal for server and client-side XML application development. In addition to a wide range of 3rd party technologies, the Java Software Platform has several optional packages available for building XML-based applications..."
