Package org.springframework.remoting.httpinvoker

Remoting classes for transparent Java-to-Java remoting via HTTP invokers.

See:
Description

Interface Summary

HttpInvokerClientConfiguration	Configuration interface for executing HTTP invoker requests.
HttpInvokerRequestExecutor	Strategy interface for actual execution of an HTTP invoker request.

Class Summary

AbstractHttpInvokerRequestExecutor	Abstract base implementation of the HttpInvokerRequestExecutor interface.
CommonsHttpInvokerRequestExecutor	HttpInvokerRequestExecutor implementation that uses Jakarta Commons HttpClient to execute POST requests.
HttpInvokerClientInterceptor	Interceptor for accessing an HTTP invoker service.
HttpInvokerProxyFactoryBean	Factory bean for HTTP invoker proxies.
HttpInvokerServiceExporter	Web controller that exports the specified service bean as HTTP invoker service endpoint, accessible via an HTTP invoker proxy.
SimpleHttpInvokerRequestExecutor	HttpInvokerRequestExecutor implementation that uses standard J2SE facilities to execute POST requests, without support for HTTP authentication or advanced configuration options.

Package org.springframework.remoting.httpinvoker Description

Remoting classes for transparent Java-to-Java remoting via HTTP invokers. Uses Java serialization just like RMI, but provides the same ease of setup as Caucho's HTTP-based Hessian and Burlap protocols.

HTTP invoker is the recommended protocol for Java-to-Java remoting. It is more powerful and more extensible than Hessian and Burlap, at the expense of being tied to Java. Neverthelesss, it is as easy to set up as Hessian and Burlap, which is its main advantage compared to RMI.