See: Description
Interface | Description |
---|---|
HttpInvokerClientConfiguration |
Configuration interface for executing HTTP invoker requests.
|
HttpInvokerRequestExecutor |
Strategy interface for actual execution of an HTTP invoker request.
|
Class | Description |
---|---|
AbstractHttpInvokerRequestExecutor |
Abstract base implementation of the HttpInvokerRequestExecutor interface.
|
HttpComponentsHttpInvokerRequestExecutor |
HttpInvokerRequestExecutor implementation that uses
Apache HttpComponents HttpClient
to execute POST requests. |
HttpInvokerClientInterceptor |
MethodInterceptor for accessing an
HTTP invoker service. |
HttpInvokerProxyFactoryBean |
FactoryBean for HTTP invoker proxies. |
HttpInvokerServiceExporter |
Servlet-API-based HTTP request handler that exports the specified service bean
as HTTP invoker service endpoint, accessible via an HTTP invoker proxy.
|
SimpleHttpInvokerRequestExecutor |
HttpInvokerRequestExecutor implementation
that uses standard Java facilities to execute POST requests, without support for HTTP
authentication or advanced configuration options. |
SimpleHttpInvokerServiceExporter | Deprecated
as of Spring Framework 5.1, in favor of
HttpInvokerServiceExporter |
HTTP invoker is the recommended protocol for Java-to-Java remoting. It is more powerful and more extensible than Hessian, at the expense of being tied to Java. Nevertheless, it is as easy to set up as Hessian, which is its main advantage compared to RMI.