Camel allows OGNL to be used as an Expression or Predicate the DSL or Xml Configuration.
You could use OGNL to create an Predicate in a Message Filter or as an Expression for a Recipient List
You can use OGNL dot notation to invoke operations. If you for instance have a body that contains a POJO that has a
getFamilyName method then you can construct the syntax as follows:
"request.body.familyName" // or "getRequest().getBody().getFamilyName()"
the Exchange is the root object
the Exchange object
the Exchange exception (if any)
the exchange id
the Fault message (if any)
the exchange.in message
the exchange.out message (if any)
the exchange properties
the property by the given name
the property by the given name as the given type
For example you could use OGNL inside a Message Filter in XML
<route> <from uri="seda:foo"/> <filter> <ognl>request.headers.foo == 'bar'</ognl> <to uri="seda:bar"/> </filter> </route>
And the sample using Java DSL:
from("seda:foo").filter().ognl("request.headers.foo == 'bar'").to("seda:bar");
Loading script from external resource
Available as of Camel 2.11
You can externalize the script and have Camel load it from a resource such as
This is done using the following syntax:
"resource:scheme:location", eg to refer to a file on the classpath you can do:
To use OGNL in your camel routes you need to add the a dependency on camel-ognl which implements the OGNL language.
If you use maven you could just add the following to your pom.xml, substituting the version number for the latest & greatest release (see the download page for the latest versions).
<dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-ognl</artifactId> <version>x.x.x</version> </dependency>
Otherwise, you'll also need OGNL