See: Description
Interface | Description |
---|---|
HttpInvokerClientConfiguration | Deprecated
as of 5.3 (phasing out serialization-based remoting)
|
HttpInvokerRequestExecutor | Deprecated
as of 5.3 (phasing out serialization-based remoting)
|
Class | Description |
---|---|
AbstractHttpInvokerRequestExecutor | Deprecated
as of 5.3 (phasing out serialization-based remoting)
|
HttpComponentsHttpInvokerRequestExecutor | Deprecated
as of 5.3 (phasing out serialization-based remoting)
|
HttpInvokerClientInterceptor | Deprecated
as of 5.3 (phasing out serialization-based remoting)
|
HttpInvokerProxyFactoryBean | Deprecated
as of 5.3 (phasing out serialization-based remoting)
|
HttpInvokerServiceExporter | Deprecated
as of 5.3 (phasing out serialization-based remoting)
|
SimpleHttpInvokerRequestExecutor | Deprecated
as of 5.3 (phasing out serialization-based remoting)
|
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.