POJO support

ServiceMix provides support for JBI POJOs in addition to the usual JBI Components. JBI Components are maybe not as lightweight as they could be; there's a bunch of methods on there for dealing with metadata, management and capabilities along with a lifecycle object.

ServiceMix introduces the idea of a JBI POJO which is any Java object which implements the ComponentLifeCycle interface and uses dependency injection to configure itself.

Adding an instance of ComponentLifeCycle to the SpringJBIContainer will automatically wrap the POJO in a JBI ComponentAdaptor so that it faithfully obeys the JBI Component contract.

This means you can write JBI POJOs to be deployed by Spring without deriving from some helper base class like ServiceMix's ComponentSupport so that your POJO has no dependency other than on the JBI APIs and then let ServiceMix take care of more of the plumbing for you.

Example POJO Components

First here's how we configure the two components in ServiceMix. Notice that ServiceMix is doing the routing here using destinationService.

Now lets look at the sender POJO. The sendMessages() method will send messages onto the JBI bus to the destination service specified in the above XML.

Then the receiver processes inbound messages as follows.

Being even more POJO

The code above may seem a bit too verbose for you. Firstly you can reduce much code by reusing the Component helper classes.

Another option is to be even more POJO-like. If you just want to invoke operations on the JBI bus then there's no need for you to implement the JBI component or lifecycle contract - you can just reuse the Client API.

For example this POJO sends messages into the JBI bus.

And this is a POJO receiver which just consumes the messages its given, without explicitly implementing the component or lifecycle interfaces