Java Web Services in a Nutshell

Name

TypeMappingRegistry

Synopsis

public interface TypeMappingRegistry extends java.io.Serializable {
// Public Instance Methods
    public abstract void clear(  ); 
    public abstract TypeMapping createTypeMapping(  ); 
    public abstract TypeMapping getDefaultTypeMapping(  ); 
    public abstract String[ ] getRegisteredEncodingStyleURIs(  );
    public abstract TypeMapping getTypeMapping(String encodingStyleURI); 
    public abstract TypeMapping register(String encodingStyleURI, 
        TypeMapping mapping); 
    public abstract void registerDefault(TypeMapping mapping); 
    public abstract boolean removeTypeMapping(TypeMapping mapping);
    public abstract TypeMapping unregisterTypeMapping(String encodingStyleURI); 
}

As its name suggests, the TypeMappingRegistry interface represents a registry for TypeMapping objects. On the client side, a TypeMappingRegistry is associated with a Service object, and a reference to the single instance for that Service can be obtained by calling its getTypeMappingRegistry( ) method. On the server side, each service implementation has its own TypeMappingRegistry that is created by the code for the tie classes that is generated by utilities such as wsdeploy or j2eec, which are described in Chapter 8.

A TypeMappingRegistry maintains a set of mappings from URIs that represent encoding styles to the TypeMapping objects that know how to encode and decode Java types using the rules of that encoding. A typical example of an encoding style URI is http://schemas.xmlsoap.org/soap/encoding/, which represents the ...