Since we're on a major migration process of this website, some component documents here are out of sync right now. In the meantime you may want to look at the asciidoc in the repository:

How does Camel compare to ServiceMix EIP

ServiceMix EIP was the ancestor though they both do similar things.

The main difference with ServiceMix EIP is its integrated into the existing ServiceMix XBean XML configuration whereas Camel has more Enterprise Integration Patterns and can be used outside of JBI (e.g. just with pure JMS or MINA). Also Camel supports a Java DSL or XML configuration.

Converting from ServiceMix EIP to Camel

Here's an example of a servicemix-eip route

<eip:message-filter service="test:messageFilter" endpoint="endpoint">
    <eip:exchange-target service="test:trace3" />
    <eip:xpath-predicate xpath="count(/test:world) = 1" namespaceContext="#nsContext"/>

Here's the equivalent Camel code in XML

  <from uri="jbi:endpoint:test:messageFilter:endpoint">
   <xpath>count(/test:world) = 1</xpath>
   <to uri="jbi:service:test:trace3"/>

Or Java

  filter(ns.xpath("count(/test:world) = 1")).

See Also

© 2004-2015 The Apache Software Foundation.
Apache Camel, Camel, Apache, the Apache feather logo, and the Apache Camel project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.
Graphic Design By Hiram