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.
| HttpInvokerClientConfiguration | Configuration interface for executing HTTP invoker requests. | 
| HttpInvokerRequestExecutor | Strategy interface for actual execution of an HTTP invoker request. | 
| AbstractHttpInvokerRequestExecutor | Abstract base implementation of the HttpInvokerRequestExecutor interface. | 
| CommonsHttpInvokerRequestExecutor | HttpInvokerRequestExecutorimplementation that uses
 Jakarta Commons HttpClient
 to execute POST requests. | 
| HttpInvokerClientInterceptor | org.aopalliance.intercept.MethodInterceptor for accessing an HTTP invoker service. | 
| HttpInvokerProxyFactoryBean | FactoryBeanfor 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 J2SE facilities to execute POST requests, without support for HTTP authentication or advanced configuration options. | 
| SimpleHttpInvokerServiceExporter | HTTP request handler that exports the specified service bean as HTTP invoker service endpoint, accessible via an HTTP invoker proxy. |