Language
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 camel-core and hence no additional JARs is needed. You only have to include additional Camel components if the language of choice mandates it, such as using Groovy or JavaScript languages.
URI format
language://languageName[:script][?options]
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
language://languageName:resource:scheme:location][?options]
URI Options
The component supports the following options.
Name | Default Value | Type | Description |
|---|---|---|---|
|
|
| The name of the Language to use, such as |
|
|
| The script to execute. |
|
|
| Whether or not the result of the script should be used as the new message body. By setting to |
|
|
| Camel 2.9: Whether to cache the script if loaded from a resource. |
|
|
| Camel 2.13/2.12.2/2.11.3: Whether to cache the compiled script. Turning this option on can gain performance as the script is only compiled/created once, and reuse when processing Camel messages. But this may cause side-effects with data left from previous evaluation spills into the next, and concurrency issues as well. If the script being evaluated is idempotent then this option can be turned on. |
|
|
| Camel 2.14.1: Whether the script is binary content. This is intended to be used for loading resources using the Constant language, such as loading binary files. |
Message Headers
The following message headers can be used to affect the behavior of the component
Header | Description |
|---|---|
| The script to execute provided in the header. Takes precedence over script configured on the endpoint. |
Examples
For example you can use the Simple language to Message Translator a message:
<foo> tag.Object out = producer.requestBodyAndHeader("language:xpath", "<foo>Hello World</foo>", Exchange.LANGUAGE_SCRIPT, "/foo/text()");
assertEquals("Hello World", out);
Loading scripts from resources
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 Exchange.LANGUAGE_SCRIPT header.
The uri must start with one of the following schemes: file:, classpath:, or http:
For example to load a script from the classpath:
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:
"resource:" as shown below: