Bean Integration

Bean Integration

Camel supports the integration of beans with Camel message exchanges in a number of ways.

Bean Component

The Bean component supports the creation of a proxy via ProxyHelper to a Java interface; which the implementation just sends a message containing a BeanInvocation to some camel endpoint. Then there is a server side implementation which consumes a message and binds the message to a method parameter.

Bean Post Processor

If a bean is defined in Spring XML and it has some Camel annotations then it can be processed to inject resources (such as configured instances of CamelTemplate or Producer) or the bean can be automatically registered as a consumer.

Spring Remoting

We support a Spring Remoting provider which uses Camel as the underlying transport mechanism. The nice thing about this approach is we can use any of the Camel transport Components to communicate between beans. It also means we can use Content Based Routing and the other Enterprise Integration Patterns in between the beans; in particular we can use Message Translator to be able to convert what the on-the-wire messages look like in addition to adding various headers and so forth.