...
Variable | Type | Description |
---|---|---|
id | String | the input message id |
body | Object | the input body |
in.body | Object | the input body |
out.body | Object | the output body |
header.foo | Object | refer to the input foo header |
headers.foo | Object | refer to the input foo header |
in.header.foo | Object | refer to the input foo header |
in.headers.foo | Object | refer to the input foo header |
out.header.foo | Object | refer to the out header foo |
out.headers.foo | Object | refer to the out header foo |
property.foo | Object | refer to the foo property on the exchange |
sys.foo | String | refer to the system property |
exception.message | String | New in Camel 2.0. Refer to the exception.messsage on the exchange, is <tt>null</tt> if no exception set on exchange |
date:command:pattern | String | New in Camel 1.5. Date formatting using the |
bean:bean expression | Object | New in Camel 1.5. Invoking a bean expression using the Bean language. Specifying a method name you must use dot as separator. In Camel 2.0 we also support the ?method=methodname syntax that is used by the Bean component. |
Samples
In the Spring XML sample below we filter based on a header value:
...
Code Block | ||||
---|---|---|---|---|
| ||||
from("direct:order").transform().simple("OrderId: ${bean:orderIdGenerator.generateId}").to("mock:reply");
|
And in Camel 2.0 we can use the ?method=methodname
option that we are familiar with the Bean component itself:
Code Block | ||||
---|---|---|---|---|
| ||||
from("direct:order").transform().simple("OrderId: ${bean:orderIdGenerator?method=generateId}").to("mock:reply");
|
...