Java Web Services in a Nutshell

Name

Connection

Synopsis

public interface Connection {
// Public Instance Methods
    public abstract void close(  ) throws JAXRException;           // L0
    public abstract Set getCredentials(  ) throws JAXRException;   // L0
    public abstract RegistryService getRegistryService(  ) 
      throws JAXRException;                               // L0
    public abstract boolean isClosed(  ) 
      throws JAXRException;                               // L0
    public abstract boolean isSynchronous(  ) throws JAXRException;  // L0
    public abstract void setCredentials(Set credentials) throws JAXRException;       // L0
    public abstract void setSynchronous(boolean sync) 
      throws JAXRException;                               // L0
}

The Connection interface represents a logical connection between a JAXR client and a JAXR provider. Although the client and provider may reside in separate processes or separate systems, in general, they are co-located; therefore, method calls made by a JAXR client are handled directly by the provider. The provider, however, is not normally in the same Java VM as the registry itself and is responsible for using whatever communication mechanism is necessary to access the registry. This is typically JAX-RPC or SAAJ, using SOAP as the underlying messaging protocol. A Connection object is obtained from a ConnectionFactory and is specific to one type of registry. That is, all Connection objects returned from a UDDI implementation of ConnectionFactory support only communication with a UDDI registry.

Once you have a Connection, if the registry that you wish to communicate with requires authentication of its users, you ...