Package com.sun.xml.ws.transport.local

Transport implementations that work inside the single JVM.

See:
Description

Interface Summary

ClosedCallback

Called when the connection is closed.

Class Summary

FileSystemResourceLoader	ResourceLoader that deals with the expanded image of a war file on a file system.
InVmServer	In-VM transport.
InVmTransportFactory	TransportTubeFactory that recognizes "in-vm://inVmServerId[?portLocalName]".
LocalAsyncTransportTube	Transport Tube that routes a message to a service that runs within it.
LocalConnectionImpl	WSHTTPConnection implemented for the local transport.
LocalTransportFactory	TransportPipeFactory for the local transport.
LocalTransportTube	Transport Tube that routes a message to a service that runs within it.

Package com.sun.xml.ws.transport.local Description

Transport implementations that work inside the single JVM. Useful for testing.

Transports implemented in this package work off the exploded war file image in the file system — it should have the same file layout that you deploy into, say, Tomcat. They then look for WEB-INF/sun-jaxws.xml to determine what services are in the application, and then deploy them in a servlet-like environment.

This package comes with two transports. One is the legacy "local" transport, which effectively deploys a new service instance every time you create a new proxy/dispatch. This is not only waste of computation, but it prevents services of the same application from talking with each other.

The "in-vm" transport is the modern version of the local transport that fixes this problem. You first deploy a new application by using InVmServer, obtain its address, configure the JAX-WS RI with that endpoint, then use that to talk to the running service.