com.sun.xml.ws.api.server

Since this class mostly concerns itself with converting a transport-specific message representation to a Packet , the name is the "adapter".

The purpose of this class is twofolds:

1. To hide the logic of converting a transport-specific connection to a Packet and do the other way around.
2. To manage thread-unsafe resources, such as WSEndpoint.PipeHead , and Codec .

Adapter s are extended to work with each kind of transport, and therefore Adapter class itself is not all that useful by itself --- it merely provides a design template that can be followed.

For managing resources, an adapter uses an object called Toolkit (think of it as a tray full of tools that a dentist uses --- trays are identical, but each patient has to get one.

Applications that use the JAX-WS RI can implement this interface instead of Provider to implement asynchronous web services (AWS.) AWS enables applications to perform operations with long latency without blocking a thread, and thus particularly suitable for highly scalable service implementation, at the expesnce of implementation complexity.

Often technologies that are built on top of JAX-WS (such as Tango) needs to negotiate private contracts between them and the container.

This interface is implemented by the caller of SDDocument.writeTo method so that the SDDocument can correctly produce references to other documents.

This mechanism allows the user of WSEndpoint to assign logical URLs to each SDDocument (which is often necessarily done in a transport-dependent way), and then serve description documents.

Usage Example 1

HTTP servlet transport chose to expose those metadata documents to HTTP GET requests where each SDDocument is identified by a simple query string "?ID".

The JAX-WS spec always use a singleton instance to serve all the requests, but this hook provides a convenient way to route messages to a proper receiver.

Externally, an instance of InstanceResolver is associated with WSEndpoint .

Possible Uses

One can use WS-Addressing message properties to decide which instance to deliver a message.

When service class is annotated with an annotation that has InstanceResolverAnnotation as meta annotation, the JAX-WS RI runtime will use the instance resolver class specified on InstanceResolverAnnotation.value() .

The InstanceResolver class must have the public constructor that takes Class , which represents the type of the service.

See Stateful for a real example.

This object can be obtained from Container.getSPI(Class) .

The scope of the module is driven by W3CEndpointReferenceBuilder.build 's requirement that we need to identify a WSEndpoint that has a specific service/port name.

For JavaEE containers this should be scoped to a JavaEE application.

If Container.getSPI(Class) returns a valid instance of ResourceInjector , The JAX-WS RI will call the ResourceInjector.inject method for each service endpoint instance that it manages.

This abstract class could be implemented by appliations, or one of the SDDocumentSource.create methods can be used.

A description consists of a set of SDDocument , which each represents a single XML document that forms a part of the descriptor (for example, WSDL might refer to separate schema documents, or a WSDL might refer to another WSDL.)

ServiceDefinition and its descendants are immutable read-only objects.

When the user application calls a method on WebServiceContext , the JAX-WS RI goes to the Packet that represents the request, then check Packet.webServiceContextDelegate , and forwards the method calls to WebServiceContextDelegate .

One instance of WSEndpoint is created for each deployed service endpoint.