[CONF] Apache Camel: Content Enricher (page edited)

Mon, 14 Jul 2008 07:36:33 -0700

Page Edited : CAMEL : Content Enricher

Content Enricher has been edited by James Strachan (Jul 14, 2008).

(View changes)

Content:

Content Enricher

Camel supports the Content Enricher from the EIP patterns using a Message Translator or by using an artibrary Processor in the routing logic to enrich the message.

Using the Fluent Builders

You can use Templating to consume a message from one destination, transform it with something like Velocity or XQuery and then send it on to another destination. For example using InOnly (one way messaging)

from("activemq:My.Queue").
  to("velocity:com/acme/MyResponse.vm").
  to("activemq:Another.Queue");


If you want to use InOut (request-reply) semantics to process requests on the My.Queue queue on ActiveMQ with a template generated response, then sending responses back to the JMSReplyTo Destination you could use this.





from("activemq:My.Queue").
  to("velocity:com/acme/MyResponse.vm");





Here is a simple example using the DSL directly to transform the message body





from("direct:start").setBody(body().append(" World!")).to("mock:result");





In this example we add our own Processor using explicit Java code




from("direct:start").process(new Processor() {
    public void process(Exchange exchange) {
        Message in = exchange.getIn();
        in.setBody(in.getBody(String.class) + " World!");
    }
}).to("mock:result");





Finally we can use Bean Integration to use any Java method on any bean to act as the transformer





from("activemq:My.Queue").
  beanRef("myBeanName", "myMethodName").
  to("activemq:Another.Queue");





For further examples of this pattern in use you could look at one of the JUnit tests






Using Spring XML





<route>
  <from uri="activemq:Input"/>
  <bean ref="myBeanName" method="doTransform"/>
  <to uri="activemq:Output"/>
</route>






Using This Pattern



If you would like to use this EIP Pattern then please read the Getting Started, you may also find the Architecture useful particularly the description of Endpoint and URIs. Then you could try out some of the Examples first before trying this pattern out.

Powered by Atlassian Confluence (Version: 2.2.9 Build:#527 Sep 07, 2006) - Bug/feature request

Unsubscribe or edit your notifications preferences

Reply via email to