29.4. Expressions

download PDF


The simple language provides various elementary expressions that return different parts of a message exchange. For example, the expression, simple("${header.timeOfDay}"), would return the contents of a header called timeOfDay from the incoming message.
Since Apache Camel 2.9, you must always use the placeholder syntax, ${Expression}, to return a variable value. It is never permissible to omit the enclosing tokens (${ and }).

Contents of a single variable

You can use the simple language to define string expressions, based on the variables provided. For example, you can use a variable of the form, in.header.HeaderName, to obtain the value of the HeaderName header, as follows:

Variables embedded in a string

You can embed simple variables in a string expression—for example:
simple("Received a message from ${in.header.user} on ${}.")

date and bean variables

As well as providing variables that access all of the different parts of an exchange (see Table 29.1, “Variables for the Simple Language”), the simple language also provides special variables for formatting dates, date:command:pattern, and for calling bean methods, bean:beanRef. For example, you can use the date and the bean variables as follows:
simple("Todays date is ${date:now:yyyyMMdd}")
simple("The order type is ${bean:orderService?method=getOrderType}")

Specifying the result type

You can specify the result type of an expression explicitly. This is mainly useful for converting the result type to a boolean or numerical type.
In the Java DSL, specify the result type as an extra argument to simple(). For example, to return an integer result, you could evaluate a simple expression as follows:
.setHeader("five", simple("5", Integer.class))
In the XML DSL, specify the result type using the resultType attribute. For example:
<setHeader headerName="five">
  <!-- use resultType to indicate that the type should be a java.lang.Integer --> 
  <simple resultType="java.lang.Integer">5</simple>

Nested expressions

Simple expressions can be nested—for example:

Accessing constants or enums

You can access a bean's constant or enum fields using the following syntax:
For example, consider the following Java enum type:
package org.apache.camel.processor;
public enum Customer {
You can access the Customer enum fields, as follows:
        .when().simple("${header.customer} ==
        .when().simple("${header.customer} ==

OGNL expressions

The Object Graph Navigation Language (OGNL) is a notation for invoking bean methods in a chain-like fashion. If a message body contains a Java bean, you can easily access its bean properties using OGNL notation. For example, if the message body is a Java object with a getAddress() accessor, you can access the Address object and the Address object's properties as follows:
Where the notation, ${body.address.street}, is shorthand for ${body.getAddress.getStreet}.

OGNL null-safe operator

You can use the null-safe operator, ?., to avoid encountering null-pointer exceptions, in case the body does not have an address. For example:
If the body is a java.util.Map type, you can look up a value in the map with the key, foo, using the following notation:

OGNL list element access

You can also use square brackets notation, [k], to access the elements of a list. For example:
The last keyword returns the index of the last element of a list. For example, you can access the second last element of a list, as follows:
You can use the size method to query the size of a list, as follows:

OGNL array length access

You can access the length of a Java array through the length method, as follows:
String[] lines = new String[]{"foo", "bar", "cat"};

simple("There are ${body.length} lines")
Red Hat logoGithubRedditYoutubeTwitter


Try, buy, & sell


About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.