Modified: websites/production/camel/content/book-languages-appendix.html
==============================================================================
--- websites/production/camel/content/book-languages-appendix.html (original)
+++ websites/production/camel/content/book-languages-appendix.html Tue Dec 2
17:19:37 2014
@@ -1041,269 +1041,124 @@ result = body * 2 + 1
</dependency>
]]></script>
</div></div>
-<h2 id="BookLanguagesAppendix-SimpleExpressionLanguage">Simple Expression
Language</h2>
-
-<p>The Simple Expression Language was a really simple language you can use,
but has since grown more powerful. Its primarily intended for being a really
small and simple language for evaluating <a shape="rect"
href="expression.html">Expression</a> and <a shape="rect"
href="predicate.html">Predicate</a> without requiring any new dependencies or
knowledge of <a shape="rect" href="xpath.html">XPath</a>; so its ideal for
testing in camel-core. Its ideal to cover 95% of the common use cases when you
need a little bit of expression based script in your Camel routes.</p>
-
-<p>However for much more complex use cases you are generally recommended to
choose a more expressive and powerful language such as: </p>
-<ul><li><a shape="rect" href="spel.html">SpEL</a></li><li><a shape="rect"
href="mvel.html">Mvel</a></li><li><a shape="rect"
href="groovy.html">Groovy</a></li><li><a shape="rect"
href="javascript.html">JavaScript</a></li><li><a shape="rect"
href="el.html">EL</a></li><li><a shape="rect"
href="ognl.html">OGNL</a></li><li>one of the supported <a shape="rect"
href="scripting-languages.html">Scripting Languages</a></li></ul>
-
-
-<p>The simple language uses <code>${body</code>} placeholders for complex
expressions where the expression contains constant literals. The ${ }
placeholders can be omitted if the expression is only the token itself.</p>
-
- <div class="aui-message success shadowed information-macro">
+<h2 id="BookLanguagesAppendix-SimpleExpressionLanguage">Simple Expression
Language</h2><p>The Simple Expression Language was a really simple language you
can use, but has since grown more powerful. Its primarily intended for being a
really small and simple language for evaluating <a shape="rect"
href="expression.html">Expression</a> and <a shape="rect"
href="predicate.html">Predicate</a> without requiring any new dependencies or
knowledge of <a shape="rect" href="xpath.html">XPath</a>; so its ideal for
testing in camel-core. Its ideal to cover 95% of the common use cases when you
need a little bit of expression based script in your Camel
routes.</p><p>However for much more complex use cases you are generally
recommended to choose a more expressive and powerful language such
as:</p><ul><li><a shape="rect" href="spel.html">SpEL</a></li><li><a
shape="rect" href="mvel.html">Mvel</a></li><li><a shape="rect"
href="groovy.html">Groovy</a></li><li><a shape="rect"
href="javascript.html">Java
Script</a></li><li><a shape="rect" href="el.html">EL</a></li><li><a
shape="rect" href="ognl.html">OGNL</a></li><li>one of the supported <a
shape="rect" href="scripting-languages.html">Scripting
Languages</a></li></ul><p>The simple language uses <code>${body</code>}
placeholders for complex expressions where the expression contains constant
literals. The ${ } placeholders can be omitted if the expression is only the
token itself.</p> <div class="aui-message success shadowed
information-macro">
<p class="title">Alternative syntax</p>
<span class="aui-icon icon-success">Icon</span>
<div class="message-content">
-
-<p>From Camel 2.5 onwards you can also use the alternative syntax which uses
$simple{ } as placeholders.<br clear="none">
-This can be used in situations to avoid clashes when using for example Spring
property placeholder together with Camel.</p>
+ <p>From Camel 2.5 onwards you can also use the
alternative syntax which uses $simple{ } as placeholders.<br clear="none"> This
can be used in situations to avoid clashes when using for example Spring
property placeholder together with Camel.</p>
</div>
</div>
-
-
<div class="aui-message success shadowed information-macro">
<p class="title">Configuring result type</p>
<span class="aui-icon icon-success">Icon</span>
<div class="message-content">
-
-<p>From Camel 2.8 onwards you can configure the result type of the <a
shape="rect" href="simple.html">Simple</a> expression. For example to set the
type as a <code>java.lang.Boolean</code> or a <code>java.lang.Integer</code>
etc.</p>
+ <p>From Camel 2.8 onwards you can configure the
result type of the <a shape="rect" href="simple.html">Simple</a> expression.
For example to set the type as a <code>java.lang.Boolean</code> or a
<code>java.lang.Integer</code> etc.</p>
</div>
</div>
-
-
<div class="aui-message hint shadowed information-macro">
<p class="title">File language is now merged with Simple
language</p>
<span class="aui-icon icon-hint">Icon</span>
<div class="message-content">
-
-<p>From Camel 2.2 onwards, the <a shape="rect" href="file-language.html">File
Language</a> is now merged with <a shape="rect" href="simple.html">Simple</a>
language which means you can use all the file syntax directly within the simple
language.</p>
+ <p>From Camel 2.2 onwards, the <a shape="rect"
href="file-language.html">File Language</a> is now merged with <a shape="rect"
href="simple.html">Simple</a> language which means you can use all the file
syntax directly within the simple language.</p>
</div>
</div>
-
-
<div class="aui-message hint shadowed information-macro">
<p class="title">Simple Language Changes in Camel 2.9
onwards</p>
<span class="aui-icon icon-hint">Icon</span>
<div class="message-content">
-
-<p>The <a shape="rect" href="simple.html">Simple</a> language have been
improved from Camel 2.9 onwards to use a better syntax parser, which can do
index precise error messages, so you know exactly what is wrong and where the
problem is. For example if you have made a typo in one of the operators, then
previously the parser would not be able to detect this, and cause the
evaluation to be true. There is a few changes in the syntax which are no longer
backwards compatible. When using <a shape="rect" href="simple.html">Simple</a>
language as a <a shape="rect" href="predicate.html">Predicate</a> then the
literal text <strong>must</strong> be enclosed in either single or double
quotes. For example: <code>"${body} == 'Camel'"</code>. Notice how we have
single quotes around the literal. The old style of using <code>"body"</code>
and <code>"header.foo"</code> to refer to the message body and header is
@deprecated, and its encouraged to always use ${ } tokens for the built-in
functions.<br c
lear="none">
-The range operator now requires the range to be in single quote as well as
shown: <code>"${header.zip} between '30000..39999'"</code>. </p>
+ <p>The <a shape="rect"
href="simple.html">Simple</a> language have been improved from Camel 2.9
onwards to use a better syntax parser, which can do index precise error
messages, so you know exactly what is wrong and where the problem is. For
example if you have made a typo in one of the operators, then previously the
parser would not be able to detect this, and cause the evaluation to be true.
There is a few changes in the syntax which are no longer backwards compatible.
When using <a shape="rect" href="simple.html">Simple</a> language as a <a
shape="rect" href="predicate.html">Predicate</a> then the literal text
<strong>must</strong> be enclosed in either single or double quotes. For
example: <code>"${body} == 'Camel'"</code>. Notice how we have single quotes
around the literal. The old style of using <code>"body"</code> and
<code>"header.foo"</code> to refer to the message body and header is
@deprecated, and its encouraged to always use ${ } tokens for
the built-in functions.<br clear="none"> The range operator now requires the
range to be in single quote as well as shown: <code>"${header.zip} between
'30000..39999'"</code>.</p>
</div>
</div>
-
-
-<p>To get the body of the in message: <code>"body"</code>, or
<code>"in.body"</code> or <code>"${body}"</code>.</p>
-
-<p>A complex expression must use ${ } placeholders, such as: <code>"Hello
${in.header.name} how are you?"</code>.</p>
-
-<p>You can have multiple functions in the same expression: <code>"Hello
${in.header.name} this is ${in.header.me} speaking"</code>.<br clear="none">
-However you can <strong>not</strong> nest functions in Camel 2.8.x or older
(i.e. having another ${ } placeholder in an existing, is not allowed).<br
clear="none">
-From <strong>Camel 2.9</strong> onwards you can nest functions.</p>
-
-<h3 id="BookLanguagesAppendix-Variables.4">Variables</h3>
-
-<div class="confluenceTableSmall">
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th
colspan="1" rowspan="1" class="confluenceTh"><p> Variable </p></th><th
colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> camelId </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> String </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.10:</strong>
the <a shape="rect" href="camelcontext.html">CamelContext</a> name
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
camelContext.<strong>OGNL</strong> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> Object </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>Camel 2.11:</strong> the CamelContext invoked
using a Camel OGNL expression. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> exchangeId </p></td><td cols
pan="1" rowspan="1" class="confluenceTd"><p> String </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <strong>Camel 2.3:</strong> the exchange
id </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> id
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> String
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> the input message
id </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> body
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Object
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> the input body
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> in.body
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Object
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> the input body
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
body.<strong>OGNL</strong> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> Object
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel
2.3:</strong> the input body invoked using a Camel OGNL expression.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
in.body.<strong>OGNL</strong> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> Object </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>Camel 2.3:</strong> the input body invoked
using a Camel OGNL expression. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> bodyAs(<em>type</em>) </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> Type </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>Camel 2.3:</strong> Converts the body to the
given type determined by its classname. The converted body can be null.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
mandatoryBodyAs(<em>type</em>) </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> Type </p></td><td colspan="
1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.5:</strong> Converts
the body to the given type determined by its classname, and expects the body to
be not null. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> out.body </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> Object </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> the output body </p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> header.foo </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> Object </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> refer to the input foo header
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
header[foo] </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
Object </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
<strong>Camel 2.9.2:</strong> refer to the input foo header
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
headers.foo
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Object
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> refer to the
input foo header </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> headers[foo] </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> Object </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>Camel 2.9.2:</strong> refer to the input foo
header </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
in.header.foo </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
Object </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> refer to
the input foo header </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> in.header[foo] </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> Object </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>Camel 2.9.2:</strong> refer to the input foo
header </p></td></tr><tr><td colspan="1" rows
pan="1" class="confluenceTd"><p> in.headers.foo </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> Object </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> refer to the input foo header
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
in.headers[foo] </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
Object </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
<strong>Camel 2.9.2:</strong> refer to the input foo header
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
header.foo[bar] </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
Object </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
<strong>Camel 2.3:</strong> regard input foo header as a map and perform lookup
on the map with bar as key </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> in.header.foo[bar] </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> Object </p></td><td colspan="1" r
owspan="1" class="confluenceTd"><p> <strong>Camel 2.3:</strong> regard input
foo header as a map and perform lookup on the map with bar as key
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
in.headers.foo[bar] </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> Object </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>Camel 2.3:</strong> regard input foo header as
a map and perform lookup on the map with bar as key </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>
header.foo.<strong>OGNL</strong> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> Object </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>Camel 2.3:</strong> refer to the input foo
header and invoke its value using a Camel OGNL expression.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
in.header.foo.<strong>OGNL</strong> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> Object </p>
</td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel
2.3:</strong> refer to the input foo header and invoke its value using a Camel
OGNL expression. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> in.headers.foo.<strong>OGNL</strong> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> Object </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.3:</strong>
refer to the input foo header and invoke its value using a Camel OGNL
expression. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> out.header.foo </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> Object </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> refer to the out header foo </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> out.header[foo] </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> Object </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.9
.2:</strong> refer to the out header foo </p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> out.headers.foo </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> Object </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> refer to the out header foo
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
out.headers[foo] </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
Object </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
<strong>Camel 2.9.2:</strong> refer to the out header foo </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>
headerAs(<em>key</em>,<em>type</em>) </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> Type </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>Camel 2.5:</strong> Converts the header to the
given type determined by its classname </p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> headers </p></td><td colspan="1
" rowspan="1" class="confluenceTd"><p> Map </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <strong>Camel 2.9:</strong> refer to the
input headers </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> in.headers </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> Map </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>Camel 2.9:</strong> refer to the input headers
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
property.foo </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
Object </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> refer to
the foo property on the exchange </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> property[foo] </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> Object </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>Camel 2.9.2:</strong> refer to the foo
property on the exchange </p></td></tr><tr><td colsp
an="1" rowspan="1" class="confluenceTd"><p> property.foo.<strong>OGNL</strong>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Object
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel
2.8:</strong> refer to the foo property on the exchange and invoke its value
using a Camel OGNL expression. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> sys.foo </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> String </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> refer to the system property </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> sysenv.foo </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> String </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.3:</strong>
refer to the system environment </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> exception </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> Object </p
></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel
>2.4:</strong> Refer to the exception object on the exchange, is
><strong>null</strong> if no exception set on exchange. Will fallback and grab
>caught exceptions (<code>Exchange.EXCEPTION_CAUGHT</code>) if the Exchange
>has any. </p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p> exception.<strong>OGNL</strong> </p></td><td
>colspan="1" rowspan="1" class="confluenceTd"><p> Object </p></td><td
>colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.4:</strong>
>Refer to the exchange exception invoked using a Camel OGNL expression object
></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
>exception.message </p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p> String </p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p> Refer to the exception.message on the exchange, is
><strong>null</strong> if no exception set on exchange. Will fallback and grab
>caught exc
eptions (<code>Exchange.EXCEPTION_CAUGHT</code>) if the Exchange has any.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
exception.stacktrace </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> String </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>Camel 2.6.</strong> Refer to the
exception.stracktrace on the exchange, is <strong>null</strong> if no exception
set on exchange. Will fallback and grab caught exceptions
(<code>Exchange.EXCEPTION_CAUGHT</code>) if the Exchange has any.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
date:<em>command:pattern</em> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> String </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> Date formatting using the
<code>java.text.SimpleDataFormat</code> patterns. Supported commands are:
<strong>now</strong> for current timestamp, <strong>in.header.xxx</strong> or
<strong>header.xxx</strong> to use the Date o
bject in the IN header with the key xxx. <strong>out.header.xxx</strong> to
use the Date object in the OUT header with the key xxx.</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> bean:<em>bean expression</em>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Object
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Invoking a bean
expression using the <a shape="rect" href="bean.html">Bean</a> language.
Specifying a method name you must use dot as separator. We also support the
?method=methodname syntax that is used by the <a shape="rect"
href="bean.html">Bean</a> component. </p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> properties:<em>locations:key</em>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> String
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel
2.3:</strong> Lookup a property with the given key. The <code>locations</code>
option is optional. See more at <a shape=
"rect" href="using-propertyplaceholder.html">Using PropertyPlaceholder</a>.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> routeId
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> String
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel
2.11:</strong> Returns the id of the current route the <a shape="rect"
href="exchange.html">Exchange</a> is being routed. </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> threadName </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> String </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.3:</strong>
Returns the name of the current thread. Can be used for logging purpose.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> ref:xxx
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Object
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel
2.6:</strong> To lookup a bean from t
he <a shape="rect" href="registry.html">Registry</a> with the given id.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
type:name.field </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
Object </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
<strong>Camel 2.11:</strong> To refer to a type or field by its FQN name. To
refer to a field you can append .FIELD_NAME. For example you can refer to the
constant field from Exchange as:
<code>org.apache.camel.Exchange.FILE_NAME</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>.</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> null </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>Camel 2.12.3:</strong> represents a
<strong>null</strong> </p></td></tr></tbody></table></div>
-</div>
-
-<h3 id="BookLanguagesAppendix-OGNLexpressionsupport">OGNL expression
support</h3>
-<p><strong>Available as of Camel 2.3</strong></p>
-
- <div class="aui-message hint shadowed information-macro">
+<p>To get the body of the in message: <code>"body"</code>, or
<code>"in.body"</code> or <code>"${body}"</code>.</p><p>A complex expression
must use ${ } placeholders, such as: <code>"Hello ${in.header.name} how are
you?"</code>.</p><p>You can have multiple functions in the same expression:
<code>"Hello ${in.header.name} this is ${in.header.me} speaking"</code>.<br
clear="none"> However you can <strong>not</strong> nest functions in Camel
2.8.x or older (i.e. having another ${ } placeholder in an existing, is not
allowed).<br clear="none"> From <strong>Camel 2.9</strong> onwards you can nest
functions.</p><h3 id="BookLanguagesAppendix-Variables.4">Variables</h3><div
class="confluenceTableSmall"><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Variable</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="
1" rowspan="1" class="confluenceTd"><p>camelId</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>String</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><strong>Camel 2.10:</strong> the <a shape="rect"
href="camelcontext.html">CamelContext</a> name</p></td></tr><tr><td colspan="1"
rowspan="1"
class="confluenceTd"><p>camelContext.<strong>OGNL</strong></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Object</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><strong>Camel 2.11:</strong> the
CamelContext invoked using a Camel OGNL expression.</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>exchangeId</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>String</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><strong>Camel 2.3:</strong> the exchange
id</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>id</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>String</p></td><td colspan="
1" rowspan="1" class="confluenceTd"><p>the input message
id</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>body</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Object</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>the input body</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>in.body</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Object</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>the input body</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>body.<strong>OGNL</strong></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Object</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><strong>Camel 2.3:</strong> the input body
invoked using a Camel OGNL expression.</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>in.body.<strong>OGNL</strong></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Object</p></td><td colspan="1"
rowspan
="1" class="confluenceTd"><p><strong>Camel 2.3:</strong> the input body
invoked using a Camel OGNL expression.</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>bodyAs(<em>type</em>)</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Type</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><strong>Camel 2.3:</strong> Converts the
body to the given type determined by its classname. The converted body can be
null.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>mandatoryBodyAs(<em>type</em>)</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Type</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><strong>Camel 2.5:</strong> Converts the body to the
given type determined by its classname, and expects the body to be not
null.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>out.body</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Object</p></td><td colspan="1" rowspan="1" class="co
nfluenceTd"><p>the output body</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>header.foo</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Object</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>refer to the input foo header</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>header[foo]</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Object</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><strong>Camel 2.9.2:</strong> refer to the
input foo header</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>headers.foo</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Object</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>refer to the input foo header</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>headers[foo]</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Object</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><strong>Camel
2.9.2:</strong> refer to the input foo header</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>in.header.foo</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Object</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>refer to the input foo header</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>in.header[foo]</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Object</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><strong>Camel 2.9.2:</strong> refer to the
input foo header</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>in.headers.foo</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Object</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>refer to the input foo header</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>in.headers[foo]</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Object</p></td><td colspan="1"
rowspan="1" class="conf
luenceTd"><p><strong>Camel 2.9.2:</strong> refer to the input foo
header</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>header.foo[bar]</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Object</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><strong>Camel 2.3:</strong> regard input foo header as
a map and perform lookup on the map with bar as key</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>in.header.foo[bar]</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Object</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><strong>Camel 2.3:</strong> regard input
foo header as a map and perform lookup on the map with bar as
key</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>in.headers.foo[bar]</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Object</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><strong>Camel 2.3:</strong> regard input foo header as
a map and pe
rform lookup on the map with bar as key</p></td></tr><tr><td colspan="1"
rowspan="1"
class="confluenceTd"><p>header.foo.<strong>OGNL</strong></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Object</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><strong>Camel 2.3:</strong> refer to the
input foo header and invoke its value using a Camel OGNL
expression.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>in.header.foo.<strong>OGNL</strong></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Object</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><strong>Camel 2.3:</strong> refer to the
input foo header and invoke its value using a Camel OGNL
expression.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>in.headers.foo.<strong>OGNL</strong></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Object</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><strong>Camel 2.3:</strong> refer to the in
put foo header and invoke its value using a Camel OGNL
expression.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>out.header.foo</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Object</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>refer to the out header foo</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>out.header[foo]</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Object</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><strong>Camel 2.9.2:</strong> refer to the
out header foo</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>out.headers.foo</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Object</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>refer to the out header foo</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>out.headers[foo]</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Object</p></td><td colspan="1"
rows
pan="1" class="confluenceTd"><p><strong>Camel 2.9.2:</strong> refer to the out
header foo</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>headerAs(<em>key</em>,<em>type</em>)</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Type</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><strong>Camel 2.5:</strong> Converts the
header to the given type determined by its classname</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>headers</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Map</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><strong>Camel 2.9:</strong> refer to the input
headers</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>in.headers</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Map</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><strong>Camel 2.9:</strong> refer to the input
headers</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><
p>property.foo</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Object</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>refer to the foo property on the
exchange</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>property[foo]</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Object</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><strong>Camel 2.9.2:</strong> refer to the foo property
on the exchange</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>property.foo.<strong>OGNL</strong></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Object</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><strong>Camel 2.8:</strong> refer to the
foo property on the exchange and invoke its value using a Camel OGNL
expression.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>sys.foo</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>String</p></td><td colspan="1" rowspan="1
" class="confluenceTd"><p>refer to the system property</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>sysenv.foo</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>String</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><strong>Camel 2.3:</strong> refer to the
system environment</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>exception</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Object</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><strong>Camel 2.4:</strong> Refer to the exception
object on the exchange, is <strong>null</strong> if no exception set on
exchange. Will fallback and grab caught exceptions
(<code>Exchange.EXCEPTION_CAUGHT</code>) if the Exchange has
any.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>exception.<strong>OGNL</strong></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Object</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><
strong>Camel 2.4:</strong> Refer to the exchange exception invoked using a
Camel OGNL expression object</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>exception.message</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>String</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Refer to the exception.message on the exchange, is
<strong>null</strong> if no exception set on exchange. Will fallback and grab
caught exceptions (<code>Exchange.EXCEPTION_CAUGHT</code>) if the Exchange has
any.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>exception.stacktrace</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>String</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><strong>Camel 2.6.</strong> Refer to the
exception.stracktrace on the exchange, is <strong>null</strong> if no exception
set on exchange. Will fallback and grab caught exceptions
(<code>Exchange.EXCEPTION_CAUGHT</code>) if the Exchange has any.</p><
/td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>date:<em>command:pattern</em></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>String</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Date formatting using the
<code>java.text.SimpleDataFormat</code> patterns. Supported commands are:
<strong>now</strong> for current timestamp, <strong>in.header.xxx</strong> or
<strong>header.xxx</strong> to use the Date object in the IN header with the
key xxx. <strong>out.header.xxx</strong> to use the Date object in the OUT
header with the key xxx.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>bean:<em>bean expression</em></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Object</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Invoking a bean expression using the <a shape="rect"
href="bean.html">Bean</a> language. Specifying a method name you must use dot
as separator. We also support the ?method=methodname syntax tha
t is used by the <a shape="rect" href="bean.html">Bean</a>
component.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>properties:<em>locations:key</em></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>String</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><strong>Deprecated (use properties-location
instead) Camel 2.3:</strong> Lookup a property with the given key. The
<code>locations</code> option is optional. See more at <a shape="rect"
href="using-propertyplaceholder.html">Using
PropertyPlaceholder</a>.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>properties-location:<em><a shape="rect"
class="external-link" href="http://locationskey";
rel="nofollow">locations:key</a></em></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>String</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><strong>Camel 2.14.1:</strong> Lookup a property with
the given key. The <code>locations</code> option is optional. See
more at <a shape="rect" href="using-propertyplaceholder.html">Using
PropertyPlaceholder</a>.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd">properties:key:default</td><td colspan="1" rowspan="1"
class="confluenceTd">String</td><td colspan="1" rowspan="1"
class="confluenceTd"><strong>Camel 2.14.1</strong>: Lookup a property with the
given key. If the key does not exists or has no value, then an optional default
value can be specified.</td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>routeId</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>String</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><strong>Camel 2.11:</strong> Returns the id of the
current route the <a shape="rect" href="exchange.html">Exchange</a> is being
routed.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>threadName</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>String</p></td><td colspan="1" rowspan="1"
class="confluenceTd"
><p><strong>Camel 2.3:</strong> Returns the name of the current thread. Can be
>used for logging purpose.</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p>ref:xxx</p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p>Object</p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p><strong>Camel 2.6:</strong> To lookup a bean from the
><a shape="rect" href="registry.html">Registry</a> with the given
>id.</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p>type:name.field</p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p>Object</p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p><strong>Camel 2.11:</strong> To refer to a type or
>field by its FQN name. To refer to a field you can append .FIELD_NAME. For
>example you can refer to the constant field from Exchange as:
><code>org.apache.camel.Exchange.FILE_NAME</code></p></td><td colspan="1"
>rowspan="1" class="confluenceTd"><p>.</p></td></tr><tr><td colspan="1"
>rowspan="1" class="co
nfluenceTd"><p>null</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><strong>Camel 2.12.3:</strong> represents a
<strong>null</strong></p></td></tr></tbody></table></div></div><h3
id="BookLanguagesAppendix-OGNLexpressionsupport">OGNL expression
support</h3><p><strong>Available as of Camel 2.3</strong></p> <div
class="aui-message hint shadowed information-macro">
<span class="aui-icon icon-hint">Icon</span>
<div class="message-content">
-
-<p>Camel's OGNL support is for invoking methods only. You cannot access
fields.<br clear="none">
-From <strong>Camel 2.11.1</strong> onwards we added special support for
accessing the length field of Java arrays.</p>
+ <p>Camel's OGNL support is for invoking methods
only. You cannot access fields.<br clear="none"> From <strong>Camel
2.11.1</strong> onwards we added special support for accessing the length field
of Java arrays.</p>
</div>
</div>
-
-
-<p>The <a shape="rect" href="simple.html">Simple</a> and <a shape="rect"
href="bean.html">Bean</a> language now supports a Camel OGNL notation for
invoking beans in a chain like fashion.<br clear="none">
-Suppose the Message IN body contains a POJO which has a
<code>getAddress()</code> method.</p>
-
-<p>Then you can use Camel OGNL notation to access the address object:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-simple("${body.address}")
+<p>The <a shape="rect" href="simple.html">Simple</a> and <a shape="rect"
href="bean.html">Bean</a> language now supports a Camel OGNL notation for
invoking beans in a chain like fashion.<br clear="none"> Suppose the Message IN
body contains a POJO which has a <code>getAddress()</code> method.</p><p>Then
you can use Camel OGNL notation to access the address object:</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[simple("${body.address}")
simple("${body.address.street}")
simple("${body.address.zip}")
]]></script>
-</div></div>
-
-<p>Camel understands the shorthand names for getters, but you can invoke any
method or use the real name such as:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-simple("${body.address}")
+</div></div><p>Camel understands the shorthand names for getters, but you can
invoke any method or use the real name such as:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[simple("${body.address}")
simple("${body.getAddress.getStreet}")
simple("${body.address.getZip}")
simple("${body.doSomething}")
]]></script>
-</div></div>
-
-<p>You can also use the null safe operator (<code>?.</code>) to avoid NPE if
for example the body does NOT have an address</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-simple("${body?.address?.street}")
+</div></div><p>You can also use the null safe operator (<code>?.</code>) to
avoid NPE if for example the body does NOT have an address</p><div class="code
panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[simple("${body?.address?.street}")
]]></script>
-</div></div>
-
-<p>Its also possible to index in <code>Map</code> or <code>List</code> types,
so you can do:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-simple("${body[foo].name}")
+</div></div><p>Its also possible to index in <code>Map</code> or
<code>List</code> types, so you can do:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[simple("${body[foo].name}")
]]></script>
-</div></div>
-<p>To assume the body is <code>Map</code> based and lookup the value with
<code>foo</code> as key, and invoke the <code>getName</code> method on that
value.</p>
-
- <div class="aui-message hint shadowed information-macro">
+</div></div><p>To assume the body is <code>Map</code> based and lookup the
value with <code>foo</code> as key, and invoke the <code>getName</code> method
on that value.</p> <div class="aui-message hint shadowed information-macro">
<span class="aui-icon icon-hint">Icon</span>
<div class="message-content">
-
-<p>If the key has space, then you <strong>must</strong> enclose the key with
quotes, for example 'foo bar':</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-simple("${body['foo bar'].name}")
+ <p>If the key has space, then you
<strong>must</strong> enclose the key with quotes, for example 'foo
bar':</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[simple("${body['foo
bar'].name}")
]]></script>
</div></div>
</div>
</div>
-
-
-<p>You can access the <code>Map</code> or <code>List</code> objects directly
using their key name (with or without dots) :</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-simple("${body[foo]}")
+<p>You can access the <code>Map</code> or <code>List</code> objects directly
using their key name (with or without dots) :</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[simple("${body[foo]}")
simple("${body[this.is.foo]}")
]]></script>
-</div></div>
-
-<p>Suppose there was no value with the key <code>foo</code> then you can use
the null safe operator to avoid the NPE as shown:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-simple("${body[foo]?.name}")
+</div></div><p>Suppose there was no value with the key <code>foo</code> then
you can use the null safe operator to avoid the NPE as shown:</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[simple("${body[foo]?.name}")
]]></script>
-</div></div>
-
-<p>You can also access <code>List</code> types, for example to get lines from
the address you can do:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-simple("${body.address.lines[0]}")
+</div></div><p>You can also access <code>List</code> types, for example to get
lines from the address you can do:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[simple("${body.address.lines[0]}")
simple("${body.address.lines[1]}")
simple("${body.address.lines[2]}")
]]></script>
-</div></div>
-
-<p>There is a special <code>last</code> keyword which can be used to get the
last value from a list.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-simple("${body.address.lines[last]}")
+</div></div><p>There is a special <code>last</code> keyword which can be used
to get the last value from a list.</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[simple("${body.address.lines[last]}")
]]></script>
-</div></div>
-
-<p>And to get the 2nd last you can subtract a number, so we can use
<code>last-1</code> to indicate this:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-simple("${body.address.lines[last-1]}")
+</div></div><p>And to get the 2nd last you can subtract a number, so we can
use <code>last-1</code> to indicate this:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[simple("${body.address.lines[last-1]}")
]]></script>
-</div></div>
-
-<p>And the 3rd last is of course:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-simple("${body.address.lines[last-2]}")
+</div></div><p>And the 3rd last is of course:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[simple("${body.address.lines[last-2]}")
]]></script>
-</div></div>
-
-<p>And you can call the size method on the list with</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-simple("${body.address.lines.size}")
+</div></div><p>And you can call the size method on the list with</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[simple("${body.address.lines.size}")
]]></script>
-</div></div>
-
-<p>From <strong>Camel 2.11.1</strong> onwards we added support for the length
field for Java arrays as well, eg:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-String[] lines = new String[]{"foo", "bar",
"cat"};
+</div></div><p>From <strong>Camel 2.11.1</strong> onwards we added support for
the length field for Java arrays as well, eg:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[String[] lines = new
String[]{"foo", "bar", "cat"};
exchange.getIn().setBody(lines);
simple("There are ${body.length} lines")
]]></script>
-</div></div>
-
-<p>And yes you can combine this with the operator support as shown below:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-simple("${body.address.zip} > 1000")
+</div></div><p>And yes you can combine this with the operator support as shown
below:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[simple("${body.address.zip} >
1000")
]]></script>
-</div></div>
-
-<h3 id="BookLanguagesAppendix-Operatorsupport">Operator support</h3>
-<p>The parser is limited to only support a single operator. </p>
-
-<p>To enable it the left value must be enclosed in ${ }. The syntax is:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-${leftValue} OP rightValue
+</div></div><h3 id="BookLanguagesAppendix-Operatorsupport">Operator
support</h3><p>The parser is limited to only support a single
operator.</p><p>To enable it the left value must be enclosed in ${ }. The
syntax is:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[${leftValue} OP rightValue
]]></script>
-</div></div>
-<p>Where the <code>rightValue</code> can be a String literal enclosed in
<code>' '</code>, <code>null</code>, a constant value or another expression
enclosed in ${ }.</p>
-
- <div class="aui-message hint shadowed information-macro">
+</div></div><p>Where the <code>rightValue</code> can be a String literal
enclosed in <code>' '</code>, <code>null</code>, a constant value or another
expression enclosed in ${ }.</p> <div class="aui-message hint shadowed
information-macro">
<p class="title">Important</p>
<span class="aui-icon icon-hint">Icon</span>
<div class="message-content">
-
-<p>There <strong>must</strong> be spaces around the operator.</p>
+ <p>There <strong>must</strong> be spaces around
the operator.</p>
</div>
</div>
-
-
-<p>Camel will automatically type convert the rightValue type to the leftValue
type, so its able to eg. convert a string into a numeric so you can use >
comparison for numeric values.</p>
-
-<p>The following operators are supported:</p>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th
colspan="1" rowspan="1" class="confluenceTh"><p> Operator </p></th><th
colspan="1" rowspan="1" class="confluenceTh"><p> Description
</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> ==
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> equals
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> >
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> greater than
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> >=
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> greater than or
equals </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
< </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> less than
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <=
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> less than or
equals </p></td></tr><tr><td colspan="1
" rowspan="1" class="confluenceTd"><p> != </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> not equals </p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> contains </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> For testing if contains in a string based
value </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
not contains </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> For
testing if not contains in a string based value </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> regex </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> For matching against a given regular
expression pattern defined as a String value </p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> not regex </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> For not matching against a given regular
expression pattern defined as a String value </p></td></tr><tr><td colspan="1"
rowspan="1
" class="confluenceTd"><p> in </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> For matching if in a set of values, each element must
be separated by comma. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> not in </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> For matching if not in a set of values, each element
must be separated by comma. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> is </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> For matching if the left hand side type is an
instanceof the value. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> not is </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> For matching if the left hand side type is not an
instanceof the value. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> range </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> For matching if the left hand side is within a range
of values defined as numbers: <code>from..to</code>. From <strong>Camel
2.9</strong> onwards the range values must be enclosed in single quotes.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> not
range </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> For
matching if the left hand side is not within a range of values defined as
numbers: <code>from..to</code>. From <strong>Camel 2.9</strong> onwards the
range values must be enclosed in single quotes.
</p></td></tr></tbody></table></div>
-
-
-<p>And the following unary operators can be used:</p>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th
colspan="1" rowspan="1" class="confluenceTh"><p> Operator </p></th><th
colspan="1" rowspan="1" class="confluenceTh"><p> Description
</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> ++
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel
2.9:</strong> To increment a number by one. The left hand side must be a
function, otherwise parsed as literal. </p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> -- </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>Camel 2.9:</strong> To decrement a number by
one. The left hand side must be a function, otherwise parsed as literal.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> \
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel
2.9.3 to 2.10.x</strong> To escape a value, eg \$, to indicate a $ sign.
Special: Use \n for new line, \t for tab, and \r
for carriage return. <strong>Notice:</strong> Escaping is <strong>not</strong>
supported using the <a shape="rect" href="file-language.html">File
Language</a>. <strong>Notice:</strong> From Camel 2.11 onwards the escape
character is no longer support, but replaced with the following three special
escaping. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> \n </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>Camel 2.11:</strong> To use newline character.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> \t
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel
2.11:</strong> To use tab character. </p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> \r </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>Camel 2.11:</strong> To use carriage return
character. </p></td></tr></tbody></table></div>
-
-
-
-<p>And the following logical operators can be used to group expressions:</p>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th
colspan="1" rowspan="1" class="confluenceTh"><p> Operator </p></th><th
colspan="1" rowspan="1" class="confluenceTh"><p> Description
</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> and
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
<strong>deprecated</strong> use && instead. The logical and operator is
used to group two expressions. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> or </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>deprecated</strong> use || instead. The
logical or operator is used to group two expressions. </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> && </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.9:</strong>
The logical and operator is used to group two expressions.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> || </p>
</td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel
2.9:</strong> The logical or operator is used to group two expressions.
</p></td></tr></tbody></table></div>
-
-
- <div class="aui-message hint shadowed information-macro">
+<p>Camel will automatically type convert the rightValue type to the leftValue
type, so its able to eg. convert a string into a numeric so you can use >
comparison for numeric values.</p><p>The following operators are
supported:</p><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Operator</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>==</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>equals</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>greater than</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>>=</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>greater than or equals</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><</p></td><td colspan="1" rowspan="1"
class="con
fluenceTd"><p>less than</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><=</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>less than or equals</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>!=</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>not equals</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>contains</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>For testing if contains in a string based
value</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>not
contains</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>For
testing if not contains in a string based value</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>regex</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>For matching against a given regular
expression pattern defined as a String value</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>not regex
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>For not matching
against a given regular expression pattern defined as a String
value</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>in</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>For matching if in a set of values, each element must
be separated by comma.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>not in</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>For matching if not in a set of values, each element
must be separated by comma.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>is</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>For matching if the left hand side type is an
instanceof the value.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>not is</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>For matching if the left hand side type is not an
instanceof the value.</p></td></tr><tr
><td colspan="1" rowspan="1" class="confluenceTd"><p>range</p></td><td
>colspan="1" rowspan="1" class="confluenceTd"><p>For matching if the left hand
>side is within a range of values defined as numbers: <code>from..to</code>.
>From <strong>Camel 2.9</strong> onwards the range values must be enclosed in
>single quotes.</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p>not range</p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p>For matching if the left hand side is not within a
>range of values defined as numbers: <code>from..to</code>. From <strong>Camel
>2.9</strong> onwards the range values must be enclosed in single
>quotes.</p></td></tr></tbody></table></div><p>And the following unary
>operators can be used:</p><div class="table-wrap"><table
>class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
>class="confluenceTh"><p>Operator</p></th><th colspan="1" rowspan="1"
>class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1"
>rowspan="1" class="
confluenceTd"><p>++</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><strong>Camel 2.9:</strong> To increment a number by
one. The left hand side must be a function, otherwise parsed as
literal.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>--</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><strong>Camel 2.9:</strong> To decrement a number by
one. The left hand side must be a function, otherwise parsed as
literal.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>\</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><strong>Camel 2.9.3 to 2.10.x</strong> To escape a
value, eg \$, to indicate a $ sign. Special: Use \n for new line, \t for tab,
and \r for carriage return. <strong>Notice:</strong> Escaping is
<strong>not</strong> supported using the <a shape="rect"
href="file-language.html">File Language</a>. <strong>Notice:</strong> From
Camel 2.11 onwards the escape character is no longer support, but replaced w
ith the following three special escaping.</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>\n</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><strong>Camel 2.11:</strong> To use newline
character.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>\t</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><strong>Camel 2.11:</strong> To use tab
character.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>\r</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><strong>Camel 2.11:</strong> To use carriage return
character.</p></td></tr></tbody></table></div><p>And the following logical
operators can be used to group expressions:</p><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Operator</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>and</p></td
><td colspan="1" rowspan="1"
>class="confluenceTd"><p><strong>deprecated</strong> use && instead.
>The logical and operator is used to group two
>expressions.</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p>or</p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p><strong>deprecated</strong> use || instead. The
>logical or operator is used to group two expressions.</p></td></tr><tr><td
>colspan="1" rowspan="1" class="confluenceTd"><p>&&</p></td><td
>colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.9:</strong>
>The logical and operator is used to group two
>expressions.</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p>||</p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p><strong>Camel 2.9:</strong> The logical or operator
>is used to group two expressions.</p></td></tr></tbody></table></div> <div
>class="aui-message hint shadowed information-macro">
<p class="title">Using and,or operators</p>
<span class="aui-icon icon-hint">Icon</span>
<div class="message-content">
-
-<p>In <strong>Camel 2.4 or older</strong> the <code>and</code> or
<code>or</code> can only be used <strong>once</strong> in a simple language
expression. From <strong>Camel 2.5</strong> onwards you can use these operators
multiple times.</p>
+ <p>In <strong>Camel 2.4 or older</strong> the
<code>and</code> or <code>or</code> can only be used <strong>once</strong> in a
simple language expression. From <strong>Camel 2.5</strong> onwards you can use
these operators multiple times.</p>
</div>
</div>
-
-
-<p>The syntax for AND is:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-${leftValue} OP rightValue and ${leftValue} OP rightValue
+<p>The syntax for AND is:</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[${leftValue} OP rightValue and ${leftValue}
OP rightValue
]]></script>
-</div></div>
-
-<p>And the syntax for OR is:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-${leftValue} OP rightValue or ${leftValue} OP rightValue
+</div></div><p>And the syntax for OR is:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[${leftValue} OP rightValue or ${leftValue} OP
rightValue
]]></script>
-</div></div>
-
-<p>Some examples:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-simple("${in.header.foo} == 'foo'")
+</div></div><p>Some examples:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[simple("${in.header.foo} ==
'foo'")
// here Camel will type convert '100' into the type of in.header.bar
and if its an Integer '100' will also be converter to an Integer
simple("${in.header.bar} == '100'")
@@ -1313,114 +1168,58 @@ simple("${in.header.bar} == 100&quo
// 100 will be converter to the type of in.header.bar so we can do >
comparison
simple("${in.header.bar} > 100")
]]></script>
-</div></div>
-
- <div class="aui-message hint shadowed information-macro">
+</div></div> <div class="aui-message hint shadowed information-macro">
<p class="title">Comparing with different types</p>
<span class="aui-icon icon-hint">Icon</span>
<div class="message-content">
-
-<p>When you compare with different types such as String and int, then you have
to take a bit care. Camel will use the type from the left hand side as 1st
priority. And fallback to the right hand side type if both values couldn't be
compared based on that type.<br clear="none">
-This means you can flip the values to enforce a specific type. Suppose the bar
value above is a String. Then you can flip the equation:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-simple("100 < ${in.header.bar}")
+ <p>When you compare with different types such as
String and int, then you have to take a bit care. Camel will use the type from
the left hand side as 1st priority. And fallback to the right hand side type if
both values couldn't be compared based on that type.<br clear="none"> This
means you can flip the values to enforce a specific type. Suppose the bar value
above is a String. Then you can flip the equation:</p><div class="code panel
pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[simple("100 < ${in.header.bar}")
]]></script>
-</div></div>
-<p>which then ensures the int type is used as 1st priority.</p>
-
-<p>This may change in the future if the Camel team improves the binary
comparison operations to prefer numeric types over String based. It's most
often the String type which causes problem when comparing with numbers.</p>
+</div></div><p>which then ensures the int type is used as 1st
priority.</p><p>This may change in the future if the Camel team improves the
binary comparison operations to prefer numeric types over String based. It's
most often the String type which causes problem when comparing with numbers.</p>
</div>
</div>
-
-
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-// testing for null
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[// testing for null
simple("${in.header.baz} == null")
// testing for not null
simple("${in.header.baz} != null")
]]></script>
-</div></div>
-
-<p>And a bit more advanced example where the right value is another
expression</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-simple("${in.header.date} == ${date:now:yyyyMMdd}")
+</div></div><p>And a bit more advanced example where the right value is
another expression</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[simple("${in.header.date} ==
${date:now:yyyyMMdd}")
simple("${in.header.type} ==
${bean:orderService?method=getOrderType}")
]]></script>
-</div></div>
-
-<p>And an example with contains, testing if the title contains the word
Camel</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-simple("${in.header.title} contains 'Camel'")
+</div></div><p>And an example with contains, testing if the title contains the
word Camel</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[simple("${in.header.title} contains
'Camel'")
]]></script>
-</div></div>
-
-<p>And an example with regex, testing if the number header is a 4 digit
value:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-simple("${in.header.number} regex '\\d{4}'")
+</div></div><p>And an example with regex, testing if the number header is a 4
digit value:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[simple("${in.header.number} regex
'\\d{4}'")
]]></script>
-</div></div>
-
-<p>And finally an example if the header equals any of the values in the list.
Each element must be separated by comma, and no space around.<br clear="none">
-This also works for numbers etc, as Camel will convert each element into the
type of the left hand side.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-simple("${in.header.type} in 'gold,silver'")
+</div></div><p>And finally an example if the header equals any of the values
in the list. Each element must be separated by comma, and no space around.<br
clear="none"> This also works for numbers etc, as Camel will convert each
element into the type of the left hand side.</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[simple("${in.header.type} in
'gold,silver'")
]]></script>
-</div></div>
-
-<p>And for all the last 3 we also support the negate test using not:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-simple("${in.header.type} not in 'gold,silver'")
+</div></div><p>And for all the last 3 we also support the negate test using
not:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[simple("${in.header.type} not in
'gold,silver'")
]]></script>
-</div></div>
-
-<p>And you can test if the type is a certain instance, eg for instance a
String</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-simple("${in.header.type} is 'java.lang.String'")
+</div></div><p>And you can test if the type is a certain instance, eg for
instance a String</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[simple("${in.header.type} is
'java.lang.String'")
]]></script>
-</div></div>
-<p>We have added a shorthand for all <code>java.lang</code> types so you can
write it as:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-simple("${in.header.type} is 'String'")
+</div></div><p>We have added a shorthand for all <code>java.lang</code> types
so you can write it as:</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[simple("${in.header.type} is
'String'")
]]></script>
-</div></div>
-
-<p>Ranges are also supported. The range interval requires numbers and both
from and end are inclusive. For instance to test whether a value is between 100
and 199:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-simple("${in.header.number} range 100..199")
+</div></div><p>Ranges are also supported. The range interval requires numbers
and both from and end are inclusive. For instance to test whether a value is
between 100 and 199:</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[simple("${in.header.number} range
100..199")
]]></script>
-</div></div>
-<p>Notice we use <code>..</code> in the range without spaces. Its based on the
same syntax as Groovy.</p>
-
-<p>From <strong>Camel 2.9</strong> onwards the range value must be in single
quotes</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-simple("${in.header.number} range '100..199'")
+</div></div><p>Notice we use <code>..</code> in the range without spaces. Its
based on the same syntax as Groovy.</p><p>From <strong>Camel 2.9</strong>
onwards the range value must be in single quotes</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[simple("${in.header.number} range
'100..199'")
]]></script>
-</div></div>
-
-
- <div class="aui-message success shadowed information-macro">
+</div></div> <div class="aui-message success shadowed information-macro">
<p class="title">Can be used in Spring XML</p>
<span class="aui-icon icon-success">Icon</span>
<div class="message-content">
-
-<p>As the Spring XML does not have all the power as the Java DSL with all its
various builder methods, you have to resort to use some other languages<br
clear="none">
-for testing with simple operators. Now you can do this with the simple
language. In the sample below we want to test if the header is a widget order:
</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[
- <from uri="seda:orders">
+ <p>As the Spring XML does not have all the power
as the Java DSL with all its various builder methods, you have to resort to use
some other languages<br clear="none"> for testing with simple operators. Now
you can do this with the simple language. In the sample below we want to test
if the header is a widget order:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[ <from uri="seda:orders">
<filter>
<simple>${in.header.type} == 'widget'</simple>
<to uri="bean:orderService?method=handleWidget"/>
@@ -1430,150 +1229,72 @@ for testing with simple operators. Now y
</div></div>
</div>
</div>
-
-
-<h4 id="BookLanguagesAppendix-Usingand/or">Using and / or</h4>
-<p>If you have two expressions you can combine them with the <code>and</code>
or <code>or</code> operator.</p>
-
- <div class="aui-message success shadowed information-macro">
+<h4 id="BookLanguagesAppendix-Usingand/or">Using and / or</h4><p>If you have
two expressions you can combine them with the <code>and</code> or
<code>or</code> operator.</p> <div class="aui-message success shadowed
information-macro">
<p class="title">Camel 2.9 onwards</p>
<span class="aui-icon icon-success">Icon</span>
<div class="message-content">
-
-<p>Use && or || from Camel 2.9 onwards.</p>
+ <p>Use && or || from Camel 2.9 onwards.</p>
</div>
</div>
-
-
-<p>For instance:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-simple("${in.header.title} contains 'Camel' and
${in.header.type'} == 'gold'")
+<p>For instance:</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[simple("${in.header.title} contains
'Camel' and ${in.header.type'} == 'gold'")
]]></script>
-</div></div>
-
-<p>And of course the <code>or</code> is also supported. The sample would
be:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-simple("${in.header.title} contains 'Camel' or
${in.header.type'} == 'gold'")
+</div></div><p>And of course the <code>or</code> is also supported. The sample
would be:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[simple("${in.header.title} contains
'Camel' or ${in.header.type'} == 'gold'")
]]></script>
-</div></div>
-
-<p><strong>Notice:</strong> Currently <code>and</code> or <code>or</code> can
only be used <strong>once</strong> in a simple language expression. This might
change in the future.<br clear="none">
-So you <strong>cannot</strong> do:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-simple("${in.header.title} contains 'Camel' and
${in.header.type'} == 'gold' and ${in.header.number} range
100..200")
+</div></div><p><strong>Notice:</strong> Currently <code>and</code> or
<code>or</code> can only be used <strong>once</strong> in a simple language
expression. This might change in the future.<br clear="none"> So you
<strong>cannot</strong> do:</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[simple("${in.header.title} contains
'Camel' and ${in.header.type'} == 'gold' and
${in.header.number} range 100..200")
]]></script>
-</div></div>
-
-<h3 id="BookLanguagesAppendix-Samples.3">Samples</h3>
-<p>In the Spring XML sample below we filter based on a header value:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[
- <from uri="seda:orders">
[... 234 lines stripped ...]
