{"id":399,"date":"2010-08-26T22:23:52","date_gmt":"2010-08-26T20:23:52","guid":{"rendered":"http:\/\/mcl.jogger.pl\/2010\/08\/26\/complex-flows-with-apache-camel\/"},"modified":"2022-08-02T10:29:10","modified_gmt":"2022-08-02T08:29:10","slug":"complex-flows-with-apache-camel","status":"publish","type":"post","link":"https:\/\/touk.pl\/blog\/2010\/08\/26\/complex-flows-with-apache-camel\/","title":{"rendered":"Complex flows with Apache Camel"},"content":{"rendered":"

At work, we’re mainly integrating services and systems, and since we’re on a constant lookout for new, better technologies, ways to do things easier, make them more sustainable, we’re trying to Usually we use<\/p>\n

Apache Camel<\/a> for this task, which is a Swiss-knife for integration engineer. What’s more, this tools corresponds well with our approach to integration solutions:
\n* try to operate on XML messages, so you get the advantage of XPaths, XSL and other benefits,
\n* don’t convert XML into Java classes back and forth and be worried with problems like XML conversion,
\n* try to get a simple flow of the process. However, at first sight Apache Camel seems to have some drawbacks mainly in the area of practical solutions ;-). It’s very handy tool if you need to use it as a pipeline with some marginal processing of the data that passes through it. It gets a lot harder to wrap your head around if you consider some branching and intermediate calls to external services. This may be tricky to write properly in Camel’s DSL. Here is a simple pipeline example:<\/p>\n

\"\" And here the exact scenario we’re discussing: \"\" What I’d like to show is the solution to this problem. Well, if you’re using a recent version of Camel this may be easier, a little different, but should still more-or-less work this way. This code is written for Apache Camel 1.4 – a rather antic version, but that’s what we’re forced to use. Oh, well. Ok, enough whining! So, I create a test class to illustrate the case. The route defined in TestRouter<\/strong> class is responsible for:
\n1. receiving input
\n2. setting exchange property to a given xpath, which effectively is the name of the first XML element in the input stream
\n3. than, the input data is sent to three different external services, each of them replies with some fictional data – notice routes a<\/strong>, b<\/strong> and c<\/strong>. The SimpleContentSetter<\/strong> processor is just for responding with a given text.
\n4. the response from all three services is somehow processed by RequestEnricher<\/strong> bean, which is described below
\n5. eventually the exchange is logged in specified category Here is some code for this:<\/p>\n

public class SimpleTest {\r\n    public void setUp() throws Exception {\r\n        TestRouter tr = new TestRouter();\r\n        ctx.addRoutes(tr);\r\n    }\r\n\r\n    @Test\r\n    public void shouldCheck() throws Exception {\r\n        ctx.createProducerTemplate().send(\"direct:in\", getInOut(\"\"));\r\n    }\r\n\r\n    class TestRouter extends RouteBuilder {\r\n\r\n        public void configure() throws Exception {\r\n\r\n            ((ProcessorType) from(\"direct:in\")\r\n                .setProperty(\"operation\").xpath(\"local-name(\/*)\", String.class)\r\n                .multicast(new MergeAggregationStrategy())\r\n                .to(\"direct:a\", \"direct:b\", \"direct:c\")\r\n                .end()\r\n                .setBody().simple(\"${in.body}\"))\r\n            .bean(RequestEnricher.class, \"enrich\")\r\n                .to(\"log:pl.touk.debug\");\r\n\r\n            from(\"direct:a\").process(new SimpleContentSetter(\"\"));\r\n            from(\"direct:b\").process(new SimpleContentSetter(\"\"));\r\n            from(\"direct:c\").process(new SimpleContentSetter(\"\"));\r\n        }\r\n    }\r\n}<\/pre>\n
What’s unusual in this code is the fact, that what normally Camel does when you write a piece of DSL like:<\/p>\n
.to(\"direct:a\", \"direct:b\", \"direct:c\")<\/pre>\n
is pass input to service<\/p>\n
a<\/strong>, than a<\/strong>‘s output gets passed to b<\/strong>, becomes it’s input, than b<\/strong>‘s output becomes c<\/strong>‘s input. The problem being, you loose the output from a<\/strong> and b<\/strong>, not mentioning that you might want to send the same input to all three services. That’s where a little tool called multicast()<\/em> comes in handy. It offers you the ability to aggregate the outputs of those services. You may even create an AggregationStrategy<\/strong> that will do it the way you like. Below class, MergeAggregationStrategy<\/strong> does exactly that kind of work – it joins outputs from all three services. A lot of info about proper use of AggregationStrategy<\/strong>-ies can be found in this post by Torsten Mielke.<\/a><\/p>\n
public class MergeAggregationStrategy implements AggregationStrategy {\r\n\r\n    public Exchange aggregate(Exchange oldExchange, Exchange newExchange) {\r\n        if (oldExchange.isFailed()) {\r\n            return oldExchange;\r\n        }\r\n        transformMessage(oldExchange.getIn(), newExchange.getIn());\r\n        transformMessage(oldExchange.getOut(), newExchange.getOut());\r\n        return newExchange;\r\n    }\r\n\r\n    private void transformMessage(Message oldM, Message newM) {\r\n        String oldBody = oldM.getBody(String.class);\r\n        String newBody = newM.getBody(String.class);\r\n        newM.setBody(oldBody + newBody);\r\n    }\r\n\r\n}<\/pre>\n
However nice this may look (or not), what you’re left with is a mix of multiple XMLs. Normally this won’t do you much good. Better thing to do is to parse this output in some way. What we’re using for this is a Groovy :). Which is great for the task of parsing XML. A lot less verbose than ordinary Java. Let’s assume a scenario, that the aggregated output, currently looking like this:<\/p>\n
<\/pre>\n
is to be processed with the following steps in mind:<\/p>\n
    \n
  • use ** as the result element<\/li>\n
  • use attributes param1<\/em>, param2<\/em>, param3<\/em> from element ** and add it to result element **<\/li>\n<\/ul>\n
    public class RequestEnricher {\r\n\r\n    public String enrich(@Property(name = \"operation\") String operation, Exchange ex) {\r\n\r\n        use(DOMCategory) {\r\n            def dhl = new groovy.xml.Namespace(\"http:\/\/example.com\/common\/dhl\/schema\", 'dhl')\r\n            def pc = new groovy.xml.Namespace(\"http:\/\/example.com\/pc\/types\", 'pc')\r\n            def doc = new XmlParser().parseText(ex.in.body)\r\n\r\n            def pcRequest = doc.\r\n            \"aaaa\" [0]\r\n\r\n            [\"param1\", \"param2\", \"param3\"].each() {\r\n                def node = doc.\r\n                '**' [(\"\" + it)][0]\r\n                if (node)\r\n                    pcRequest['@' + it] = node.text()\r\n            }\r\n\r\n            gNodeListToString([pcRequest])\r\n        }\r\n\r\n    }\r\n\r\n    String gNodeListToString(list) {\r\n        StringBuilder sb = new StringBuilder();\r\n        list.each {\r\n            listItem ->\r\n                StringWriter sw = new StringWriter();\r\n            new XmlNodePrinter(new PrintWriter(sw)).print(listItem)\r\n            sb.append(sw.toString());\r\n        }\r\n        return sb.toString();\r\n    }\r\n\r\n}<\/pre>\n
     <\/p>\n
    What we’re doing here, especially the last line of<\/p>\n
    enrich<\/strong> method is the conversion to String. There are some problems for Camel if we spit out Groovy objects. The rest is just some Groovy specific ways of manipulating XML. But looking into enrich<\/strong> method’s parameters, there is @Property<\/em> annotation used, which binds the property assigned earlier in a router code to one of the arguments. That is really cool feature and there are more such annotations:
    \n* @XPath<\/em>
    \n* @Header<\/em>
    \n* @Headers<\/em> and @Properties<\/em> – gives whole maps of properties or headers This pretty much concludes the subject :) Have fun, and if in doubt, leave a comment with your question!<\/p>\n
    <\/p>\n","protected":false},"excerpt":{"rendered":"At work, we’re mainly integrating services and systems, and since we’re on a constant lookout for new, better technologies, ways to do things easier, make them more sustainable, we’re trying to\nUsually we use Apache Camel for this task, which is a Swis…At work, we’re mainly integrating services and systems, and since we’re on a constant lookout for new, better technologies, ways to do things easier, make them more sustainable, we’re trying to\nUsually we use Apache Camel for this task, which is a Swis…\n","protected":false},"author":11,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11],"tags":[68],"class_list":{"0":"post-399","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-development-design","7":"tag-java"},"_links":{"self":[{"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/posts\/399","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/users\/11"}],"replies":[{"embeddable":true,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/comments?post=399"}],"version-history":[{"count":10,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/posts\/399\/revisions"}],"predecessor-version":[{"id":14802,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/posts\/399\/revisions\/14802"}],"wp:attachment":[{"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/media?parent=399"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/categories?post=399"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/tags?post=399"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}