open class HttpInvokerProxyFactoryBean : HttpInvokerClientInterceptor, FactoryBean<Any>
FactoryBean for HTTP invoker proxies. Exposes the proxied service for use as a bean reference, using the specified service interface.
The service URL must be an HTTP URL exposing an HTTP invoker service. Optionally, a codebase URL can be specified for on-demand dynamic code download from a remote location. For details, see HttpInvokerClientInterceptor docs.
Serializes remote invocation objects and deserializes remote invocation result objects. Uses Java serialization just like RMI, but provides the same ease of setup as Caucho's HTTP-based Hessian protocol.
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.
WARNING: Be aware of vulnerabilities due to unsafe Java deserialization: Manipulated input streams could lead to unwanted code execution on the server during the deserialization step. As a consequence, do not expose HTTP invoker endpoints to untrusted clients but rather just between your own services. In general, we strongly recommend any other message format (e.g. JSON) instead.
Author
Juergen Hoeller
Since
1.1
See Also
#setServiceInterface#setServiceUrl#setCodebaseUrlHttpInvokerClientInterceptorHttpInvokerServiceExporterorg.springframework.remoting.rmi.RmiProxyFactoryBeanorg.springframework.remoting.caucho.HessianProxyFactoryBean
HttpInvokerProxyFactoryBean()
FactoryBean for HTTP invoker proxies. Exposes the proxied service for use as a bean reference, using the specified service interface. The service URL must be an HTTP URL exposing an HTTP invoker service. Optionally, a codebase URL can be specified for on-demand dynamic code download from a remote location. For details, see HttpInvokerClientInterceptor docs. Serializes remote invocation objects and deserializes remote invocation result objects. Uses Java serialization just like RMI, but provides the same ease of setup as Caucho's HTTP-based Hessian protocol. 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. WARNING: Be aware of vulnerabilities due to unsafe Java deserialization: Manipulated input streams could lead to unwanted code execution on the server during the deserialization step. As a consequence, do not expose HTTP invoker endpoints to untrusted clients but rather just between your own services. In general, we strongly recommend any other message format (e.g. JSON) instead. |
open fun afterPropertiesSet(): Unit |
|
open fun getObject(): Any |
|
open fun getObjectType(): Class<*> |
|
open fun isSingleton(): Boolean |