| java.lang.Object
 com.sun.xml.ws.api.client.ClientPipelineHook
| ClientPipelineHook | | abstract public class ClientPipelineHook (Code) | | Allow the container (primarily Glassfish) to inject
their own pipes into the client pipeline.
This interface has a rather ad-hoc set of methods, because
we didn't want to define an autonomous pipe-assembly process.
(We thought this is a smaller evil compared to that.)
JAX-WS obtains this through
com.sun.xml.ws.api.server.Container.getSPI(Class) .
author:
Jitendra Kotamraju |
| Method Summary | |
| public Pipe | createSecurityPipe(ClientPipeAssemblerContext ctxt, Pipe tail)
Called during the pipeline construction process once to allow a container
to register a pipe for security.
This pipe will be injected to a point very close to the transport, allowing
it to do some security operations.
Parameters:
ctxt - Represents abstraction of SEI, WSDL abstraction etc. |
| createSecurityPipe | | public Pipe createSecurityPipe(ClientPipeAssemblerContext ctxt, Pipe tail)(Code) | | Called during the pipeline construction process once to allow a container
to register a pipe for security.
This pipe will be injected to a point very close to the transport, allowing
it to do some security operations.
Parameters:
ctxt - Represents abstraction of SEI, WSDL abstraction etc. Context can be usedwhether add a new pipe to the head or not.
Parameters:
tail - Head of the partially constructed pipeline. If the implementationwishes to add new pipes, it should do so by extendingcom.sun.xml.ws.api.pipe.helper.AbstractFilterPipeImpl and making sure that this com.sun.xml.ws.api.pipe.Pipeeventually processes messages.The default implementation just returns tail, which meansno additional pipe is inserted. If the implementation addsnew pipes, return the new head pipe. |
|
|