| Root of the SPI implemented by the container
(such as application server.)
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 allows such technologies
to query the negotiated SPI by using the
Container.getSPI(Class) .
For example, if a security pipe needs to get some information
from a container, they can do the following:
- Negotiate an interface with the container and define it.
(let's call it ContainerSecuritySPI.)
- The container will implement ContainerSecuritySPI.
- At the runtime, a security pipe gets
WSEndpoint and then to
Container .
- It calls container.getSPI(ContainerSecuritySPI.class)
- The container returns an instance of ContainerSecuritySPI.
- The security pipe talks to the container through this SPI.
This protects JAX-WS from worrying about the details of such contracts,
while still providing the necessary service of hooking up those parties.
Technologies that run inside JAX-WS server runtime can access this object through
WSEndpoint.getContainer . In the client runtime, it can be accessed from
ContainerResolver.getContainer
author:
Kohsuke Kawaguchi
See Also: WSEndpoint | 