Monday, October 21, 2013

Spring Integration – Using RMI Channel Adapters

1   Introduction


This article explains how to send and receive messages over RMI using Spring Integration RMI channel adapters. It is composed of the following sections:

  • Implementing the service: The first section focuses on creating and exposing a service.
  • Implementing the client: Shows how to invoke the service using the MessagingTemplate class.
  • Abstracting SI logic: Finally, I’ve added another section explaining how to implement the same client abstracting all Spring Integration code, leaving the client focused on its business logic.

You can get the source code at github.


2   Implementing the service


This first part is pretty simple. The service is defined through annotations, so it will be autodetected by component scanning. It has a repository injected, which gets the data from an embedded database, as it will be shown in this same section:

The repository is as follows:


The following configuration exposes the service over RMI:

server-config.xml
Let’s focus on the lines with the ‘int’ namespace:

The gateway’s function is to separate the plumbing of the messaging system from the rest of the application. In this way, it gets hidden from the business logic. A gateway is bidirectional, so you have:

  • Inbound gateway: Brings a message into the application and waits for a response.
  • Outbound gateway: Invokes an external system and sends the response back to the application.


In this example, we are using a RMI inbound gateway. It will receive a message over RMI and send it to the requestEmployee channel, which is also defined here.

Finally, the service activator allows you to connect a spring bean to a message channel. Here, it is connected to the requestEmployee channel. The message will arrive to the channel and the service activator will invoke the retrieveEmployee method. Take into account that the ‘method’ attribute is not necessary if the bean has only one public method or has a method annotated with @ServiceActivator.

The response will then be sent to the reply channel. Since we didn’t define this channel, it will create a temporary reply channel.




3   Implementing the client


The client we are going to implement will invoke the service in order to retrieve an employee. To do this, it will use the MessagingTemplate class:

The client uses the messagingTemplate to convert the Integer object to a Message and send it to the local channel. As shown below, there’s an outbound gateway connected to the local channel. This outbound gateway will send the request message over RMI.



4   Abstracting SI logic


In the previous section, you may have noticed that the client class which accesses the service has Spring Integration specific logic mixed with its business code:
  • It uses the MessagingTemplate, which is a SI class.
  • It knows about the local channel, which is specific to the messaging system

In this section, I will implement this same example abstracting the messaging logic, so the client will only care about its business logic.

First, let’s take a look at the new client:

We can see now that the client just implement its business logic, without using neither message channels nor messaging template. It will just call the service interface. All the messaging definitions are in the configuration file.

client-gateway-config.xml
What we did here is add a gateway that will intercept calls to the service interface EmployeeService. Spring Integration will use the GatewayProxyFactoryBean class to create a proxy around the service interface. This proxy will use a messaging template to send the invocation to the request channel and wait for the response.



5   Conclusion


We have seen how to use Spring Integration to access a service over RMI.  We have also seen that we can not only explicitly send messages using the MessagingTemplate but also do it transparently with GatewayProxyFactoryBean.

No comments:

Post a Comment