Spring and Hessian for Fast, Easy Java Remoting

Spring and Hessian for Fast, Easy Java Remoting

he world of enterprise Java has an overwhelming array of choices for remoting: RMI, XML/SOAP, REST/JSON, etc. Each comes with its own industry-acknowledged strengths and weaknesses, such as complex setup (RMI) or performance overhead (XML/SOAP). A lesser known but very powerful and easy-to-use option is the Hessian binary web service protocol. The binary aspect of Hessian delivers excellent performance, and its native integration within Java allows you to expose remote services purely via a regular Java interface.

Hessian’s most rewarding feature, though, is the ability to pass full Java POJO object graphs from one process to another easily without the overhead of XML marshalling, an unfortunate side effect of SOAP web services. Also, Hessian is implemented in a variety of different languages, so you theoretically can execute efficient binary remoting between Java and Python or Java and C# as well.

This article walks through using the Hessian protocol as an alternative to the more widely accepted RMI, XML/SOAP, and REST/JSON approaches for remote communication. It also explains how to integrate Spring and Hessian and then create Hessian components as simple Java objects.

Basic Hessian Example

The basic Hessian setup is quite simple. You first need to externalize all the API interfaces and POJOs shared between the two endpoints into a separate JAR library, which will not contain any of the API implementation, just the interface (i.e., the contract). On the server side, Hessian provides a special HessianServlet, which you can extend to provide and expose the interface implementation. On the client side, you can use a HessianProxyFactory object to generate a local proxy of the interface from a mere URL.

The basic example from the Hessian web site illustrates this setup as follows:

Interface (shared across client and server):
public interface BasicAPI {     public String hello();}
Server implementation:
public class BasicService extends HessianServlet implements BasicAPI {  private String _greeting = "Hello, world";  public void setGreeting(String greeting)  {    _greeting = greeting;  }  public String hello()  {    return _greeting;  }}
String url = "";HessianProxyFactory factory = new HessianProxyFactory();BasicAPI basic = (BasicAPI) factory.create(BasicAPI.class, url);System.out.println("hello(): " + basic.hello());

If you have done the wsdl2java and java2wsdl Ant dance when exposing services via XML/SOAP, you surely will appreciate this straightforward path to implementing a Hessian-based web service. It’s just 100% pure Java with some magic behind the scenes to tie it all together.

Spring Hessian Integration

When implementing Hessian in a Spring application, the original Hessian API does not apply. Luckily, the Spring team realized the value of Hessian a long time ago and provided solid integration for creating Hessian components as simple Java objects?without the need to extend specialized servlets.

To demonstrate Spring’s Hessian integration, this section walks you through setting up some common interfaces. First, use the following two classes to create a service that will allow saving/updating/deleting a simple Person POJO:

public class Person implements Serializable {      private Integer id;   private String firstName;   private String lastName;   private Calendar birthDate;   public Person() {      super();   }   public Person(String firstName, String lastName, Calendar birthDate) {      super();      this.firstName = firstName;      this.lastName = lastName;      this.birthDate = birthDate;     ...getters and setters...   }}
Person DAO service:
public interface IPersonService {   Person get(Integer id);   Person add(Person person);   void delete(Integer personId);   void update(Person person);}

Both these classes are part of a common library shared on both endpoints.

Setting Up the Server Endpoint

In the Spring server-side application, create a regular Java component that implements your service interface. Here’s an example of how to do that:

@Service("personService")public class PersonService implements IPersonService {   //map used for simulating data storage     private static Map people = new ConcurrentHashMap();   private static AtomicInteger keyGenerator = new AtomicInteger(0);      @Override   public Person add(Person person) {      if (person.getId() == null) {         Integer id = keyGenerator.addAndGet(1);         person.setId(id);         people.put(id,person);         return person;      } else {         throw new RuntimeException("Person already exists!");      }         }   @Override   public void update(Person person) {      if (person.getId() != null) {         people.put(person.getId(), person);      } else {         throw new RuntimeException("Person must be saved first!");      }   }      @Override   public void delete(Integer personId) {      people.remove(personId);   }   @Override   public Person get(Integer id) {      return people.get(id);   }}

As you can see, this component does not need to extend the previously mentioned Hessian servlet. Also, the @Service Spring stereotype annotation eliminates the need to explicitly define the bean in an XML configuration. However, exposing the component via Spring does involve a series of steps.

First, in web.xml, add the Spring remoting servlet and map it to a URI:

      remoting      org.springframework.web.servlet.DispatcherServlet      1            remoting      /remoting/*   

The Spring remoting servlet will expect a new Spring application context file, which is usually called remoting-servlet.xml (separate from the usual beans.xml used by the rest of the application). In the context file, you have to expose your service via a HessianServiceExporter class:

""   xmlns:context=""   xmlns:xsi=""   xsi:schemaLocation=""
> "com.devx.hessian.server"/> "/PersonService" class="org.springframework.remoting.caucho.HessianServiceExporter"> "service" ref="personService" /> "serviceInterface" value="com.dexv.hessian.IPersonService"/>

The context elements activate Spring’s new annotation-based context support (to avoid unnecessary XML configuration) and tell it which package to use as the base for searching for components. The PersonService implementation is then injected into the HessianServiceExporter class instance.

If you run the server app (from the code sample attached to this article) and access the /remoting/PersonService URI via a regular browser, you will get a notice that Hessian is listening, although unable to process a typical browser request:

HTTP ERROR: 405HessianServiceExporter only supports POST requestsRequestURI=/remoting/PersonService

Setting Up the Client

On the client side, you need to create an instance of a HessianProxyFactoryBean that points to your service URL:

""   xmlns:context=""   xmlns:xsi=""    xsi:schemaLocation=""
> "com.devx.hessian.client" /> "personService" class="org.springframework.remoting.caucho.HessianProxyFactoryBean"> "serviceUrl" value="" /> "serviceInterface" value="com.dexv.hessian.IPersonService" />

When your service URL is defined, you can just inject the HessianProxyFactoryBean instance into your client application using regular dependency injection:

@Component("mainClient")public class MainClient {   private IPersonService service = null;      @Autowired   public void setPersonService(@Qualifier("personService") IPersonService service) {      this.service = service;   }}

Spring 2.5 and Hessian 2 Incompatibility Alert

As of version 3.2.0, the Hessian library started using a new version of the protocol called simply Hessian 2. Unfortunately, the current production version of Spring (namely 2.5.6.SEC01) has support for the original Hessian protocol only. Therefore, if you are on Spring 2.5, the version of Hessian that you should download is 3.1.6.

Fortunately, this has been corrected in the latest milestone builds of Spring 3.0. The code samples attached to this article use the latest Hessian 4.0.1 and Spring 3.0 M4 builds.


About Our Editorial Process

At DevX, we’re dedicated to tech entrepreneurship. Our team closely follows industry shifts, new products, AI breakthroughs, technology trends, and funding announcements. Articles undergo thorough editing to ensure accuracy and clarity, reflecting DevX’s style and supporting entrepreneurs in the tech sphere.

See our full editorial policy.

About Our Journalist