Java Doc for WebServiceContextDelegate.java in  » 6.0-JDK-Modules » jax-ws-runtime » com » sun » xml » ws » api » server » Java Source Code / Java DocumentationJava Source Code and Java Documentation

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 .

All the methods defined on this interface takes Packet (whose Packet.webServiceContextDelegate points to this object), so that a single stateless WebServiceContextDelegate can be used to serve multiple concurrent Packet s, if the implementation wishes to do so.

(It is also allowed to create one instance of WebServiceContextDelegate for each packet, and thus effectively ignore the packet parameter.)

Attaching this on a Packet allows Pipe s to intercept and replace them, if they wish.
author:
   Kohsuke Kawaguchi

The "address" of endpoints is always affected by a particular client being served, hence it's up to transport to provide this information.
Parameters:
  request - Always non-null.

If a transport supports publishing of WSDL by itself (instead/in addition to MEX), then it should implement this method so that the rest of the JAX-WS RI can use that information. For example, HTTP transports often use the convention getEPRAddress()+"?wsdl" for publishing WSDL on HTTP.

Some transports may not have such WSDL publishing mechanism on its own. Those transports may choose to return null, indicating that WSDL is not published.

The "address" of endpoints is always affected by a particular client being served, hence it's up to transport to provide this information.
Parameters:
  request - Always non-null. See class javadoc.
Parameters:
  endpoint - The endpoint whose address will be returned.
throws:
  WebServiceException - if this method could not compute the address for some reason.Absolute URL of the endpoint. This shold be an address that the clientcan use to talk back to this same service later.
See Also:   WebServiceContext.getEndpointReference

If a transport supports publishing of WSDL by itself (instead/in addition to MEX), then it should implement this method so that the rest of the JAX-WS RI can use that information. For example, HTTP transports often use the convention getEPRAddress()+"?wsdl" for publishing WSDL on HTTP.

Some transports may not have such WSDL publishing mechanism on its own. Those transports may choose to return null, indicating that WSDL is not published. If such transports are always used in conjunction with other transports that support WSDL publishing (such as SOAP/TCP used with Servlet transport), then such transport may choose to find the corresponding servlet endpoint by Module.getBoundEndpoints and try to obtain the address from there.

This information is used to put a metadata reference inside an EPR, among other things. Clients that do not support MEX rely on this WSDL URL to retrieve metadata, it is desirable for transports to support this, but not mandatory.

This method will be never invoked if the WSEndpoint does not have a corresponding WSDL to begin with (IOW WSEndpoint.getServiceDefinition returning null .
Parameters:
  request - Always non-null. See class javadoc.
Parameters:
  endpoint - The endpoint whose address will be returned.null if the implementation does not support the notion ofWSDL publishing.