svn commit: r983271 [4/7] - in /websites/production/camel/content: book-component-appendix.html book-in-one-page.html book-languages-appendix.html cache/main.pageCache ftp.html ftp2.html simple.html

[buildbot]

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 Sun Mar 20 
20:19:18 2016
@@ -904,7 +904,7 @@ 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">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="confluence-information-macro 
confluence-information-macro-tip"><p class="title">Alternative syntax</p><span 
class="aui-icon aui-icon-small aui-iconfont-approve 
confluence-information-macro-icon"></span><div 
class="confluence-information-macro-body"><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="confluence-information-macro co
 nfluence-information-macro-tip"><p class="title">Configuring result 
type</p><span class="aui-icon aui-icon-small aui-iconfont-approve 
confluence-information-macro-icon"></span><div 
class="confluence-information-macro-body"><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="confluence-information-macro 
confluence-information-macro-information"><p class="title">File language is now 
merged with Simple language</p><span class="aui-icon aui-icon-small 
aui-iconfont-info confluence-information-macro-icon"></span><div 
class="confluence-information-macro-body"><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 simp
 le language.</p></div></div><div class="confluence-information-macro 
confluence-information-macro-information"><p class="title">Simple Language 
Changes in Camel 2.9 onwards</p><span class="aui-icon aui-icon-small 
aui-iconfont-info confluence-information-macro-icon"></span><div 
class="confluence-information-macro-body"><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 do
 uble 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">exchange</td><td colspan="1" rowspan="1" 
class="confluenceTd">Exchange</td><td colspan="1" rowspan="1" 
class="confluenceTd"><strong>Camel 2.16:</strong> the <a shape="rect" 
href="exchange.html">Exchange</a></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd">exchange.<strong>OGNL</strong></td><td colspan="1" 
rowspan="1" class="confluenceTd">Object</td><td colspan="1" rowspan="1" 
class="confluenceTd"><strong>Camel 2.16:</strong><span> the </span><a 
shape="rect" href="exchange.html">Exchange</a><span> invoked using a Camel OGNL 
expression.</span></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>OGN
 L</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" 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="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" 
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 colspa
 n="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>O
 bject</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><strong>Deprecated:</strong> refer to the foo property 
on the exchange</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd">exchangeProperty.foo</td><td colspan="1" rowspan="1" 
class="confluenceTd">Object</td><td colspan="1" rowspan="1" 
class="confluenceTd"><span><strong>Camel 2.15:</strong> refer to the foo 
property on the exchange</span></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>Deprecated:</strong> refer to the foo property 
on the exchange</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><span>exchangeProperty[foo]</span></td><td colsp
 an="1" rowspan="1" class="confluenceTd">Object</td><td colspan="1" rowspan="1" 
class="confluenceTd"><strong>Camel 2.15:</strong><span> refer to the foo 
property on the exchange</span></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>Deprecated:</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"><span>exchangeProperty.foo.</span><strong>OGNL</strong></td><td
 colspan="1" rowspan="1" class="confluenceTd">Object</td><td colspan="1" 
rowspan="1" class="confluenceTd"><strong>Camel 2.15:</strong><span> refer to 
the foo property on the exchange and invoke its value using a Camel OGNL 
expression.</span></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="con
 fluenceTd"><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 nam
 e 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>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="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p><strong>Camel 2.12.3:</strong> represents a 
<strong>null</strong></p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p>random<em>(value)</em></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>Integer</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p><strong>Camel 2.16.0: </strong>returns a random Integer 
between 0 (included) and <em>value</em> (excluded)</p></td></tr><tr><td 
colspan="1" rowspan="1" 
class="confluenceTd"><p>random<em>(min,max)</em></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>Integer</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p><strong>Camel 2.16.0: </strong>returns a random Integer 
between <em>min</em> (included) and <em>max</em> 
(excluded)</p></td></tr><tr><td colspan="1" rowspa
 n="1" class="confluenceTd">collate(group)</td><td colspan="1" rowspan="1" 
class="confluenceTd">List</td><td colspan="1" rowspan="1" 
class="confluenceTd"><strong>Camel 2.17:</strong> The collate function iterates 
the message body and groups the data into sub lists of specified size. This can 
be used with the <a shape="rect" href="splitter.html">Splitter</a> EIP to split 
a message body and group/batch the splitted sub message into a group of N sub 
lists. This method works similar to the collate method in 
Groovy.</td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd">messageHistory</td><td colspan="1" rowspan="1" 
class="confluenceTd">String</td><td colspan="1" rowspan="1" 
class="confluenceTd"><strong>Camel 2.17:</strong> The message history of the 
current exchange how it has been routed. This is similar to the route 
stack-trace message history the error handler logs in case of an unhandled 
exception.</td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><span>messageHist
 ory(false)</span></td><td colspan="1" rowspan="1" 
class="confluenceTd">String</td><td colspan="1" rowspan="1" 
class="confluenceTd"><strong>Camel 2.17:</strong><span>&#160;</span>As 
messageHistory but without the exchange details (only includes the route 
strack-trace). This can be used if you do not want to log sensitive data from 
the message itself.</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="confluence-information-macro 
confluence-information-macro-information"><span class="aui-icon aui-icon-small 
aui-iconfont-info confluence-information-macro-icon"></span><div 
class="confluence-information-macro-body"><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" h
 ref="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">
+<h2 id="BookLanguagesAppendix-SimpleExpressionLanguage">Simple Expression 
Language</h2><p>The Simple Expression Language was a really simple language 
when it was created, but has since grown more powerful. It is primarily 
intended for being a really small and simple language for evaluating <a 
shape="rect" href="expression.html">Expression</a>s and <a shape="rect" 
href="predicate.html">Predicate</a>s without requiring any new dependencies or 
knowledge of <a shape="rect" href="xpath.html">XPath</a>; so it is ideal for 
testing in camel-core. The idea was 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="java
 script.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="confluence-information-macro confluence-information-macro-tip"><p 
class="title">Alternative syntax</p><span class="aui-icon aui-icon-small 
aui-iconfont-approve confluence-information-macro-icon"></span><div 
class="confluence-information-macro-body"><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="confluence-inf
 ormation-macro confluence-information-macro-tip"><p class="title">Configuring 
result type</p><span class="aui-icon aui-icon-small aui-iconfont-approve 
confluence-information-macro-icon"></span><div 
class="confluence-information-macro-body"><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="confluence-information-macro 
confluence-information-macro-information"><p class="title">File language is now 
merged with Simple language</p><span class="aui-icon aui-icon-small 
aui-iconfont-info confluence-information-macro-icon"></span><div 
class="confluence-information-macro-body"><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 directl
 y within the simple language.</p></div></div><div 
class="confluence-information-macro 
confluence-information-macro-information"><p class="title">Simple Language 
Changes in Camel 2.9 onwards</p><span class="aui-icon aui-icon-small 
aui-iconfont-info confluence-information-macro-icon"></span><div 
class="confluence-information-macro-body"><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 are 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 e
 ither 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 it is 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="confluence
 Td"><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">exchange</td><td colspan="1" rowspan="1" 
class="confluenceTd">Exchange</td><td colspan="1" rowspan="1" 
class="confluenceTd"><strong>Camel 2.16:</strong> the <a shape="rect" 
href="exchange.html">Exchange</a></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd">exchange.<strong>OGNL</strong></td><td colspan="1" 
rowspan="1" class="confluenceTd">Object</td><td colspan="1" rowspan="1" 
class="confluenceTd"><strong>Camel 2.16:</strong><span> the </span><a 
shape="rect" href="exchange.html">Exchange</a><span> invoked using a Camel OGNL 
expression.</span></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="confluenc
 eTd"><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" 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>i
 n.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" 
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>Objec
 t</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="confluence
 Td"><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><strong>Deprecated:</strong> refer to the foo property 
on the exchange</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd">exchangeProperty.foo</td><td colspan="1" rowspan="1" 
class="confluenceTd">Object</td><td colspan="1" rowspan="1" 
class="confluenceTd"><span><strong>Camel 2.15:</strong> refer to the foo 
property on the exchange</span></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>Deprecated:</strong> refer to the foo property 
on the exchange</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><span>exchangeProperty[foo]<
 /span></td><td colspan="1" rowspan="1" class="confluenceTd">Object</td><td 
colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.15:</strong><span> 
refer to the foo property on the exchange</span></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>Deprecated:</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"><span>exchangeProperty.foo.</span><strong>OGNL</strong></td><td
 colspan="1" rowspan="1" class="confluenceTd">Object</td><td colspan="1" 
rowspan="1" class="confluenceTd"><strong>Camel 2.15:</strong><span> refer to 
the foo property on the exchange and invoke its value using a Camel OGNL 
expression.</span></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" 
ro
 wspan="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 fall
 back 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. Spe
 cifying 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>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.1
 4.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 co
 lspan="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>null</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p><strong>Camel 2.12.3:</strong> represents a 
<strong>null</strong></p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p>random<em>(value)</em></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>Integer</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p><strong>Camel 2.16.0: </strong>returns a random Integer 
between 0 (included) and <em>value</em> (excluded)</p></td></tr><tr><td 
colspan="1" rowspan="1" 
class="confluenceTd"><p>random<em>(min,max)</em></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>Integer</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p><strong>Camel 2.16.0: </strong>returns a random Integer 
between <em>min</em> (included) and <em>max</em> (excluded)</p></td></tr><tr><t
 d colspan="1" rowspan="1" class="confluenceTd">collate(group)</td><td 
colspan="1" rowspan="1" class="confluenceTd">List</td><td colspan="1" 
rowspan="1" class="confluenceTd"><strong>Camel 2.17:</strong> The collate 
function iterates the message body and groups the data into sub lists of 
specified size. This can be used with the <a shape="rect" 
href="splitter.html">Splitter</a> EIP to split a message body and group/batch 
the splitted sub message into a group of N sub lists. This method works similar 
to the collate method in Groovy.</td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd">messageHistory</td><td colspan="1" rowspan="1" 
class="confluenceTd">String</td><td colspan="1" rowspan="1" 
class="confluenceTd"><strong>Camel 2.17:</strong> The message history of the 
current exchange how it has been routed. This is similar to the route 
stack-trace message history the error handler logs in case of an unhandled 
exception.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceT
 d"><span>messageHistory(false)</span></td><td colspan="1" rowspan="1" 
class="confluenceTd">String</td><td colspan="1" rowspan="1" 
class="confluenceTd"><strong>Camel 2.17:</strong><span>&#160;</span>As 
messageHistory but without the exchange details (only includes the route 
strack-trace). This can be used if you do not want to log sensitive data from 
the message itself.</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="confluence-information-macro 
confluence-information-macro-information"><span class="aui-icon aui-icon-small 
aui-iconfont-info confluence-information-macro-icon"></span><div 
class="confluence-information-macro-body"><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>T
 he <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="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[simple(&quot;${body.address}&quot;)
 simple(&quot;${body.address.street}&quot;)
 simple(&quot;${body.address.zip}&quot;)
@@ -918,7 +918,7 @@ simple(&quot;${body.doSomething}&quot;)
 </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="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[simple(&quot;${body?.address?.street}&quot;)
 ]]></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">
+</div></div><p>It is 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="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[simple(&quot;${body[foo].name}&quot;)
 ]]></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="confluence-information-macro 
confluence-information-macro-information"><span class="aui-icon aui-icon-small 
aui-iconfont-info confluence-information-macro-icon"></span><div 
class="confluence-information-macro-body"><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">
@@ -960,7 +960,7 @@ simple(&quot;There are ${body.length} li
 </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="brush: java; gutter: false; theme: Default" 
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="confluence-information-macro 
confluence-information-macro-information"><p class="title">Important</p><span 
class="aui-icon aui-icon-small aui-iconfont-info 
confluence-information-macro-icon"></span><div 
class="confluence-information-macro-body"><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 &gt; 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" cla
 ss="confluenceTd"><p>==</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p>equals</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd">=~</td><td colspan="1" rowspan="1" 
class="confluenceTd"><strong>Camel 2.16:</strong> equals ignore case (will 
ignore case when comparing String values)</td></tr><tr><td colspan="1" 
rowspan="1" class="confluenceTd"><p>&gt;</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p>greater than</p></td></tr><tr><td colspan="1" 
rowspan="1" class="confluenceTd"><p>&gt;=</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>&lt;</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p>less than</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p>&lt;=</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 cols
 pan="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="confl
 uenceTd"><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 th
 e 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="confluenc
 eTd"><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" rowsp
 an="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 &amp;&amp; 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>&amp;&amp;</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="confluence-information-macro 
confluence-information-macro-information"><p class="title">Using and,or 
operators</p><span class="aui-icon aui-icon-small aui-iconfont-info 
confluence-information-macro-icon"></span><div 
class="confluence-information-macro-body"><p>In <strong>Camel 2.4 or 
older</strong> the <code>and</code> or <code>or</code> can only be used 
<strong>once</str
 ong> 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">
+</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="confluence-information-macro 
confluence-information-macro-information"><p class="title">Important</p><span 
class="aui-icon aui-icon-small aui-iconfont-info 
confluence-information-macro-icon"></span><div 
class="confluence-information-macro-body"><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 it is able to eg. convert 
a string into a numeric so you can use &gt; 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" c
 lass="confluenceTd"><p>==</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p>equals</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd">=~</td><td colspan="1" rowspan="1" 
class="confluenceTd"><strong>Camel 2.16:</strong> equals ignore case (will 
ignore case when comparing String values)</td></tr><tr><td colspan="1" 
rowspan="1" class="confluenceTd"><p>&gt;</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p>greater than</p></td></tr><tr><td colspan="1" 
rowspan="1" class="confluenceTd"><p>&gt;=</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>&lt;</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p>less than</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p>&lt;=</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 co
 lspan="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="con
 fluenceTd"><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="conflue
 nceTd"><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" row
 span="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 &amp;&amp; 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" rowsp
 an="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>&amp;&amp;</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="confluence-information-macro 
confluence-information-macro-information"><p class="title">Using and,or 
operators</p><span class="aui-icon aui-icon-small aui-iconfont-info 
confluence-information-macro-icon"></span><div 
class="confluence-information-macro-body"><p>In <strong>Camel 2.4 or 
older</strong> the <code>and</code> or <code>or</code> can only be used 
<strong>once</s
 trong> 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="brush: java; gutter: false; theme: Default" 
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">
@@ -973,7 +973,7 @@ simple(&quot;${in.header.foo} == &#39;fo
 // ignore case when comparing, so if the header has value FOO this will match
 simple(&quot;${in.header.foo} =~ &#39;foo&#39;&quot;)
 
-// here Camel will type convert &#39;100&#39; into the type of in.header.bar 
and if its an Integer &#39;100&#39; will also be converter to an Integer
+// here Camel will type convert &#39;100&#39; into the type of in.header.bar 
and if it is an Integer &#39;100&#39; will also be converter to an Integer
 simple(&quot;${in.header.bar} == &#39;100&#39;&quot;)
 
 simple(&quot;${in.header.bar} == 100&quot;)
@@ -1017,7 +1017,7 @@ simple(&quot;${in.header.type} == ${bean
 </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="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[simple(&quot;${in.header.number} range 
100..199&quot;)
 ]]></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">
+</div></div><p>Notice we use <code>..</code> in the range without spaces. It 
is 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="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[simple(&quot;${in.header.number} range 
&#39;100..199&#39;&quot;)
 ]]></script>
 </div></div><div class="confluence-information-macro 
confluence-information-macro-tip"><p class="title">Can be used in Spring 
XML</p><span class="aui-icon aui-icon-small aui-iconfont-approve 
confluence-information-macro-icon"></span><div 
class="confluence-information-macro-body"><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">
@@ -1045,7 +1045,7 @@ simple(&quot;${in.header.type} == ${bean
        &lt;/filter&gt;
     &lt;/from&gt;
 ]]></script>
-</div></div><p>The Simple language can be used for the predicate test above in 
the <a shape="rect" href="message-filter.html">Message Filter</a> pattern, 
where we test if the in message has a <code>foo</code> header (a header with 
the key <code>foo</code> exists). If the expression evaluates to 
<strong>true</strong> then the message is routed to the 
<code>mock:fooOrders</code> endpoint, otherwise its lost in the deep blue sea 
<img class="emoticon emoticon-wink" 
src="https://cwiki.apache.org/confluence/s/en_GB/5982/f2b47fb3d636c8bc9fd0b11c0ec6d0ae18646be7.1/_/images/icons/emoticons/wink.png";
 data-emoticon-name="wink" alt="(wink)">.</p><p>The same example in Java 
DSL:</p><div class="code panel pdl" style="border-width: 1px;"><div 
class="codeContent panelContent pdl">
+</div></div><p>The Simple language can be used for the predicate test above in 
the <a shape="rect" href="message-filter.html">Message Filter</a> pattern, 
where we test if the in message has a <code>foo</code> header (a header with 
the key <code>foo</code> exists). If the expression evaluates to 
<strong>true</strong> then the message is routed to the 
<code>mock:fooOrders</code> endpoint, otherwise it is lost in the deep blue sea 
<img class="emoticon emoticon-wink" 
src="https://cwiki.apache.org/confluence/s/en_GB/5982/f2b47fb3d636c8bc9fd0b11c0ec6d0ae18646be7.1/_/images/icons/emoticons/wink.png";
 data-emoticon-name="wink" alt="(wink)">.</p><p>The same example in Java 
DSL:</p><div class="code panel pdl" style="border-width: 1px;"><div 
class="codeContent panelContent pdl">
 <script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[    from(&quot;seda:orders&quot;)
         
.filter().simple(&quot;${in.header.foo}&quot;).to(&quot;seda:fooOrders&quot;);
 ]]></script>
@@ -1053,23 +1053,23 @@ simple(&quot;${in.header.type} == ${bean
 <script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[   
from(&quot;direct:hello&quot;).transform().simple(&quot;Hello ${in.header.user} 
how are you?&quot;).to(&quot;mock:reply&quot;);
 ]]></script>
 </div></div><p>Notice that we must use ${ } placeholders in the expression now 
to allow Camel to parse it correctly.</p><p>And this sample uses the date 
command to output current date.</p><div class="code panel pdl" 
style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[   
from(&quot;direct:hello&quot;).transform().simple(&quot;The today is 
${date:now:yyyyMMdd} and its a great day.&quot;).to(&quot;mock:reply&quot;);
+<script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[   
from(&quot;direct:hello&quot;).transform().simple(&quot;The today is 
${date:now:yyyyMMdd} and it is a great day.&quot;).to(&quot;mock:reply&quot;);
 ]]></script>
 </div></div><p>And in the sample below we invoke the bean language to invoke a 
method on a bean to be included in the returned string:</p><div class="code 
panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[   
from(&quot;direct:order&quot;).transform().simple(&quot;OrderId: 
${bean:orderIdGenerator}&quot;).to(&quot;mock:reply&quot;);
 ]]></script>
-</div></div><p>Where <code>orderIdGenerator</code> is the id of the bean 
registered in the <a shape="rect" href="registry.html">Registry</a>. If using 
Spring then its the Spring bean id.</p><p>If we want to declare which method to 
invoke on the order id generator bean we must prepend <code>.method name</code> 
such as below where we invoke the <code>generateId</code> method.</p><div 
class="code panel pdl" style="border-width: 1px;"><div class="codeContent 
panelContent pdl">
+</div></div><p>Where <code>orderIdGenerator</code> is the id of the bean 
registered in the <a shape="rect" href="registry.html">Registry</a>. If using 
Spring then it is the Spring bean id.</p><p>If we want to declare which method 
to invoke on the order id generator bean we must prepend <code>.method 
name</code> such as below where we invoke the <code>generateId</code> 
method.</p><div class="code panel pdl" style="border-width: 1px;"><div 
class="codeContent panelContent pdl">
 <script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[   
from(&quot;direct:order&quot;).transform().simple(&quot;OrderId: 
${bean:orderIdGenerator.generateId}&quot;).to(&quot;mock:reply&quot;);
 ]]></script>
 </div></div><p>We can use the <code>?method=methodname</code> option that we 
are familiar with the <a shape="rect" href="bean.html">Bean</a> component 
itself:</p><div class="code panel pdl" style="border-width: 1px;"><div 
class="codeContent panelContent pdl">
 <script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[   
from(&quot;direct:order&quot;).transform().simple(&quot;OrderId: 
${bean:orderIdGenerator?method=generateId}&quot;).to(&quot;mock:reply&quot;);
 ]]></script>
-</div></div><p>And from Camel 2.3 onwards you can also convert the body to a 
given type, for example to ensure its a String you can do:</p><div class="code 
panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>And from Camel 2.3 onwards you can also convert the body to a 
given type, for example to ensure that&#160;it is a String you can do:</p><div 
class="code panel pdl" style="border-width: 1px;"><div class="codeContent 
panelContent pdl">
 <script class="brush: xml; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[  &lt;transform&gt;
     &lt;simple&gt;Hello ${bodyAs(String)} how are you?&lt;/simple&gt;
   &lt;/transform&gt;
 ]]></script>
-</div></div><p>There are a few types which have a shorthand notation, so we 
can use <code>String</code> instead of <code>java.lang.String</code>. These 
are: <code>byte[], String, Integer, Long</code>. All other types must use their 
FQN name, e.g. <code>org.w3c.dom.Document</code>.</p><p>Its also possible to 
lookup a value from a header <code>Map</code> in <strong>Camel 2.3</strong> 
onwards:</p><div class="code panel pdl" style="border-width: 1px;"><div 
class="codeContent panelContent pdl">
+</div></div><p>There are a few types which have a shorthand notation, so we 
can use <code>String</code> instead of <code>java.lang.String</code>. These 
are: <code>byte[], String, Integer, Long</code>. All other types must use their 
FQN name, e.g. <code>org.w3c.dom.Document</code>.</p><p>It is&#160;also 
possible to lookup a value from a header <code>Map</code> in <strong>Camel 
2.3</strong> onwards:</p><div class="code panel pdl" style="border-width: 
1px;"><div class="codeContent panelContent pdl">
 <script class="brush: xml; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[  &lt;transform&gt;
     &lt;simple&gt;The gold value is ${header.type[gold]}&lt;/simple&gt;
   &lt;/transform&gt;
@@ -1097,7 +1097,7 @@ from(&quot;direct:start&quot;)
         .otherwise()
             .to(&quot;mock:other&quot;);
 ]]></script>
-</div></div><h3 id="BookLanguagesAppendix-UsingnewlinesortabsinXMLDSLs">Using 
new lines or tabs in XML DSLs</h3><p><strong>Available as of Camel 
2.9.3</strong></p><p>From Camel 2.9.3 onwards its easier to specify new lines 
or tabs in XML DSLs as you can escape the value now</p><div class="code panel 
pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h3 id="BookLanguagesAppendix-UsingnewlinesortabsinXMLDSLs">Using 
new lines or tabs in XML DSLs</h3><p><strong>Available as of Camel 
2.9.3</strong></p><p>From Camel 2.9.3 onwards it is easier to specify new lines 
or tabs in XML DSLs as you can escape the value now</p><div class="code panel 
pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="brush: xml; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[&lt;transform&gt;
   &lt;simple&gt;The following text\nis on a new line&lt;/simple&gt;
 &lt;/transform&gt;

Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.