Available as of Camel 2.5
The language component allows you to send Exchange to an endpoint which executes a script by any of the supported Languages in Camel.
By having a component to execute language scripts, it allows more dynamic routing capabilities. For example by using the Routing Slip or Dynamic Router EIPs you can send messages to
language endpoints where the script is dynamic defined as well.
This component is provided out of the box in
And from Camel 2.11 onwards you can refer to an external resource for the script using same notation as supported by the other Languages in Camel
The component supports the following options.
The following message headers can be used to affect the behavior of the component
For example you can use the Simple language to Message Translator a message:
In case you want to convert the message body type you can do this as well:
You can also use the Groovy language, such as this example where the input message will by multiplied with 2:
You can also provide the script as a header as shown below. Here we use XPath language to extract the text from the
Object out = producer.requestBodyAndHeader("language:xpath", "<foo>Hello World</foo>", Exchange.LANGUAGE_SCRIPT, "/foo/text()"); assertEquals("Hello World", out);
Available as of Camel 2.9
You can specify a resource uri for a script to load in either the endpoint uri, or in the
The uri must start with one of the following schemes: file:, classpath:, or http:
For example to load a script from the classpath:
By default the script is loaded once and cached. However you can disable the
contentCache option and have the script loaded on each evaluation.
For example if the file myscript.txt is changed on disk, then the updated script is used:
From Camel 2.11 onwards you can refer to the resource similar to the other Languages in Camel by prefixing with
"resource:" as shown below: