Camel supports the Message Translator from the EIP patterns.

How can systems using different data formats communicate with each other using messaging?


Use a special filter, a Message Translator, between other filters or applications to translate one data format into another.

The Message Translator can be done in different ways in Camel:

  • Using Transform or Set Body in the DSL

  • Calling a Processor or bean to perform the transformation

  • Using template-based Components, with the template being the source for how the message is translated

  • Messages can also be transformed using Data Format to marshal and unmarshal messages in different encodings.

This page is documenting the first approach by using Transform EIP.


The Transform eip supports 1 options, which are listed below.

Name Description Default Type


Required Expression to return the transformed message body (the new message body to use).



Whether to disable this EIP from the route during build time. Once an EIP has been disabled then it cannot be enabled later at runtime.




Sets the description of this node.


Using Transform EIP

You can use a Transform which uses an Expression to do the transformation:

In the example below we prepend Hello to the message body using the Simple language:

    .setBody(simple("Hello ${body}"))

And in XML DSL:

    <from uri="direct:cheese"/>
        <simple>Hello ${body}</simple>
    <to uri="log:hello"/>

What is the difference between Transform and Set Body

The Transform EIP always sets the result on the OUT message body.

Set Body sets the result accordingly to the Exchange Pattern on the Exchange.