Java Web Services in a Nutshell

JAXR Registry Model Overview

A JAXR client views the registry as a set of objects whose types are defined in the javax.xml.registry.infomodel package. The information model is based on the one defined by the ebXML registry/repository specification, with some minor differences. A JAXR provider for a particular registry is required to transparently map between the JAXR information model and the real model of the registry itself, so that JAXR clients are not dependent on the details of any particular registry. This section provides an overview of the JAXR registry information model. You’ll see more detail when we look at the JAXR registry programming model later in this chapter.

Figure 7-6 shows a small part of the complete JAXR registry model, illustrating the elements that are of greatest importance to most JAXR clients. The first thing to note about this diagram is that it contains only Java interfaces. In fact, ignoring exceptions, the JAXR API contains only one class that is not an interface. The use of interfaces allows a JAXR provider to supply its own implementation classes for each element of the information model without exposing them to application code. From the client application’s point of view, this has the effect that objects within the registry cannot be created directly — instead, they are obtained from using factory methods of a class called BusinessLifeCycleManager, which will be described later in this chapter.

Figure 7-6. Organization- and Service-related registry ...