Overview of JAXR

An XML registry is an infrastructure that enables the building, deployment, and discovery of Web services. It is a neutral third party that facilitates dynamic and loosely coupled business-to-business (B2B) interactions. A registry is available to organizations as a shared resource, often in the form of a Web-based service.

Currently there are a variety of specifications for XML registries. These include

The ebXML Registry and Repository standard, which is sponsored by the Organization for the Advancement of Structured Information Standards (OASIS) and the United Nations Centre for the Facilitation of Procedures and Practices in Administration, Commerce and Transport (U.N./CEFACT)

The Universal Description, Discovery, and Integration (UDDI) project, which is being developed by a vendor consortium

A registry provider is an implementation of a business registry that conforms to a specification for XML registries.

What Is JAXR?

JAXR enables Java software programmers to use a single, easy-to-use abstraction API to access a variety of XML registries. A unified JAXR information model describes content and metadata within XML registries.

JAXR gives developers the ability to write registry client programs that are portable across various target registries. JAXR also enables value-added capabilities beyond those of the underlying registries.

The current version of the JAXR specification includes detailed bindings between the JAXR information model and both the ebXML Registry and the UDDI version 2 specifications. You can find the latest version of the specification at

At this release of the J2EE platform, JAXR implements the level 0 capability profile defined by the JAXR specification. This level allows access to both UDDI and ebXML registries at a basic level. At this release, JAXR supports access only to UDDI version 2 registries.

The Java Web Services Developer Pack (Java WSDP) Registry Server provides a UDDI version 2 registry that you can use to test your JAXR applications in a private environment. You can download the Java WSDP from http://java.sun.com/webservices/downloads/. The Registry Server includes a database based on the native XML database Xindice, which is part of the Apache XML project. This database provides the repository for registry data. The Registry Server does not support messages defined in the UDDI Version 2.0 Replication Specification.

Stop the Application Server.

Start the Java WSDP install program.

Choose the Custom install option.

When the install program requests that you choose which features to install, deselect everything except the Java WSDP Registry Server.

Select the Sun Java System Application Server Platform Edition 8 for the Web container. The Registry Server and its backing repository Xindice are installed into the Application Server as Web applications.

Start the Application Server.

Confirm that the Registry Server and Xindice Web applications are running using the Admin Console or deploytool.

Note: If you use the Java WSDP Registry Server to test JAXR applications that you develop using the Sun Java System Application Server Platform Edition 8, make sure that in your PATH you place the Application Server bin directories before the Java WSDP bin directories.

Several ebXML registries are under development, and one is available at the Center for E-Commerce Infrastructure Development (CECID), Department of Computer Science Information Systems, The University of Hong Kong (HKU). For information, see http://www.cecid.hku.hk/Release/PR09APR2002.html.

JAXR Architecture

A JAXR client: This is a client program that uses the JAXR API to access a business registry via a JAXR provider.

A JAXR provider: This is an implementation of the JAXR API that provides access to a specific registry provider or to a class of registry providers that are based on a common specification.

javax.xml.registry, which consists of the API interfaces and classes that define the registry access interface.

javax.xml.registry.infomodel, which consists of interfaces that define the information model for JAXR. These interfaces define the types of objects that reside in a registry and how they relate to each other. The basic interface in this package is the RegistryObject interface. Its subinterfaces include Organization, Service, and ServiceBinding.

Connection. The Connection interface represents a client session with a registry provider. The client must create a connection with the JAXR provider in order to use a registry.

RegistryService. The client obtains a RegistryService object from its connection. The RegistryService object in turn enables the client to obtain the interfaces it uses to access the registry.

BusinessQueryManager, which allows the client to search a registry for information in accordance with the javax.xml.registry.infomodel interfaces. An optional interface, DeclarativeQueryManager, allows the client to use SQL syntax for queries. (The implementation of JAXR in the Application Server does not implement DeclarativeQueryManager.)

BusinessLifeCycleManager, which allows the client to modify the information in a registry by either saving it (updating it) or deleting it.

When an error occurs, JAXR API methods throw a JAXRException or one of its subclasses.

Many methods in the JAXR API use a Collection object as an argument or a returned value. Using a Collection object allows operations on several registry objects at a time.

Figure 10-1 illustrates the architecture of JAXR. In the Application Server, a JAXR client uses the capability level 0 interfaces of the JAXR API to access the JAXR provider. The JAXR provider in turn accesses a registry. The Application Server supplies a JAXR provider for UDDI registries.

Overview of JAXR

What Is a Registry?

What Is JAXR?

JAXR Architecture