Burlap is a lightweight XML RPC protocol. Burlap is designed to be self-describing, eliminating the requirement for external IDLs or WSDL files. Because it is as small as possible and language-independent, non-Java Burlap implementations are can easily develop comprehensive test suites.
This tutorial only requires the open source Java implementation of the Burlap client and server included in the Hessian distribution. It can be downloaded from http://www.caucho.com/hessian/ for non-Resin clients and servers.
Because Resin's EJB implementation can use Burlap as its remote procedure call protocol, EJB developers can easily expose services to clients from other languages.
Because EJB clients and servers are written without knowledge of the underlying protocol, even if you intend to deploy with another protocol, like RMI/IIOP, you can develop using Resin's Burlap.
The Burlap 1.0 spec describes the full Burlap protocol.
A Burlap call is just an HTTP POST to a URL. The arguments are serialized into the Burlap XML format and passed to the server.
Most applications will never need to look at the Burlap protocol, but it's simple enough that a basic example can help show what's happening underneath the API.
The call does not need to specify the service name because the service is uniquely specified by the URL.
The following Addition example shows how to create a basic server so you can test Burlap.
Using Burlap requires three components:
The remote interface is used by the Hessian proxy factory to create a proxy stub implementing the service's interface.
Resin's Burlap provides a simple way of creating a server. Just extend
with your remote methods. The Burlap call will just
be a POST to that servlet. BurlapServlet will introspect the
service and expose the methods.
The Java interface describes the remote API. This example has an addition method, .
Resin's proxy client implementation uses the remote interface to expose the API to the proxy stub. Strictly speaking, though, the Java remote interface is not required for Burlap. A non-Java client will not use the Java interface, except possibly as documentation.
RPC clients follow the following steps in using a remote object: