Set Body

Camel supports the Message Translator from the EIP patterns .

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 Set Body EIP.

Options

The Set Body eip supports 0 options, which are listed below.

Name	Description	Default	Type
description	Sets the description of this node.		String
disabled	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.	false	Boolean
expression	Required Expression that returns the new body to use.		ExpressionDefinition

Name

Description

Default

Type

description

Sets the description of this node.

String

disabled

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.

false

Boolean

expression

Required Expression that returns the new body to use.

ExpressionDefinition

The Set Body eip has no exchange properties.

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

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

from("direct:cheese")
    .setBody(simple("Hello ${body}"))
    .to("log:hello");

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

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 .