Modified: websites/production/camel/content/cache/main.pageCache ============================================================================== Binary files - no diff available.
Modified: websites/production/camel/content/camel-2120-release.html ============================================================================== --- websites/production/camel/content/camel-2120-release.html (original) +++ websites/production/camel/content/camel-2120-release.html Tue Jun 25 09:18:47 2013 @@ -96,7 +96,7 @@ <p>Welcome to the 2.12.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)</p> -<ul><li><a shape="rect" href="endpoint-annotations.html" title="Endpoint Annotations">Endpoint Annotations</a> along with automatically created HTML documentation for the endpoint parameters; this makes it easier for component developers to add a few refactoring-safe annotations to their Endpoint or Consumer implementations and, (along with javadoc comments on the field or setter method), get nice user documentation on how to use the endpoint for free.</li><li><a shape="rect" href="componentconfiguration.html" title="ComponentConfiguration">ComponentConfiguration</a> API provides a handy API for tools developers to introspect on a Component to find all the possible parameters, their types and any extra annotations (like Bean Validation Annotations) to be able to create/edit endpoints or URI strings so that tools can generate nicer UIs for configuring endpoints than just letting folks edit Strings.</li><li><a shape="rect" href="endpointcompleter.html" title="EndpointCompleter ">EndpointCompleter</a> API provides a hook so that command line tools (like <a shape="rect" class="external-link" href="http://karaf.apache.org/manual/latest-2.3.x/users-guide/using-console.html";>Karaf's shell</a>), IDEs and web tools can get (bash tab like) auto-completion on endpoint paths (such as file or directory names, message queue names, database table names) when creating or using new endpoints</li><li>Reduced stack-frames in use during routing, that also makes Camel's stack traces being logged much less verbose. This also allows people to easier debug the internals of Camel as less <tt>AsyncCallback</tt> callbacks are in use during routing.</li><li>Easy to use <a shape="rect" href="message-history.html" title="Message History">Message History</a> out of the box. And included message history as "route stack-trace" when exceptions logged by <a shape="rect" href="error-handler.html" title="Error Handler">Error Handler</a> to make it easier for end users to spot where the exception occurred.</li><li><a shape="rect" href="spring-web-services.html" title="Spring Web Services">Spring Web Services</a> now supports setting/receiving SOAP headers more easily using a header on the Camel <a shape="rect" href="message.html" title="Message">Message</a>.</li><li>Evaluating <a shape="rect" href="groovy.html" title="Groovy">Groovy</a> expressions is faster as we cache the compiled scripts.</li><li>Added <tt>base64</tt> option to <a shape="rect" href="shiro-security.html" title="Shiro Security">Shiro Security</a> to allow transferring security token over <a shape="rect" href="jms.html" title="JMS">JMS</a> and other transports as base64 encoded representation.</li><li>Made it easier to use <a shape="rect" href="shiro-security.html" title="Shiro Security">Shiro Security</a> as the credentials can be provided in headers, when sending a message to a secured route.</li><li><a shape="rect" href="bindy.html" title="Bindy">Bindy</a> now supports enums.</li><l i>Added new <a shape="rect" href="backlogdebugger.html" title="BacklogDebugger">BacklogDebugger</a> to perform live debugging of messages during routing. The <a shape="rect" href="backlogdebugger.html" title="BacklogDebugger">BacklogDebugger</a> has JMX API allows tooling to control the debugger.</li><li>While using the <a shape="rect" class="external-link" href="http://xircles.codehaus.org/projects/jackson"; rel="nofollow">Jackson library</a> through the <a shape="rect" href="json.html" title="JSON">JSON</a> Dataformat there's now a <tt>jsonView</tt> attribute you could make use of directly inside the <a shape="rect" href="dsl.html" title="DSL">DSL</a> itself.</li><li><a shape="rect" href="smpp.html" title="SMPP">SMPP</a> now supports optional parameters in all commands where they are possible.</li><li><a shape="rect" href="jdbc.html" title="JDBC">JDBC</a> now supports named parameters.</li><li>Added timeout support for <a shape="rect" href="direct.html" title="Direct">Direc t</a> producers to wait for consumer to become active.</li><li>Added <tt>stats</tt> action to <a shape="rect" href="controlbus.html" title="ControlBus">ControlBus</a> to easily get performance statics in a single XML message.</li><li>Added support for request timeout on <a shape="rect" href="netty.html" title="Netty">Netty</a> producer, and to configure logging level on <a shape="rect" href="netty.html" title="Netty">Netty</a> consumer to be less noisy for ChannelClosedException which can flood the logs when client disconnects abruptly.</li><li><a shape="rect" href="springbatch.html" title="SpringBatch">Spring Batch</a> component producer now returns the <tt>JobExecution</tt> instance as the output message. Users can use the <tt>JobExecution</tt> instance to perform some operations using the Spring Batch API directly.</li><li>Added support for NULL values in <a shape="rect" href="sql-component.html" title="SQL Component">SQL</a> with named parameters.</li><li>Optimized <a sh ape="rect" href="jetty.html" title="Jetty">Jetty</a> streaming responses in non-chunked mode; and as well using buffer sizes based on <tt>HttpServletResponse.getBufferSize()</tt> instead of fixed size of 4kb.</li><li>Added <tt>greedy</tt> option to <a shape="rect" href="polling-consumer.html" title="Polling Consumer">scheduled polling consumer</a>.</li></ul> +<ul><li><a shape="rect" href="endpoint-annotations.html" title="Endpoint Annotations">Endpoint Annotations</a> along with automatically created HTML documentation for the endpoint parameters; this makes it easier for component developers to add a few refactoring-safe annotations to their Endpoint or Consumer implementations and, (along with javadoc comments on the field or setter method), get nice user documentation on how to use the endpoint for free.</li><li><a shape="rect" href="componentconfiguration.html" title="ComponentConfiguration">ComponentConfiguration</a> API provides a handy API for tools developers to introspect on a Component to find all the possible parameters, their types and any extra annotations (like Bean Validation Annotations) to be able to create/edit endpoints or URI strings so that tools can generate nicer UIs for configuring endpoints than just letting folks edit Strings.</li><li><a shape="rect" href="endpointcompleter.html" title="EndpointCompleter ">EndpointCompleter</a> API provides a hook so that command line tools (like <a shape="rect" class="external-link" href="http://karaf.apache.org/manual/latest-2.3.x/users-guide/using-console.html";>Karaf's shell</a>), IDEs and web tools can get (bash tab like) auto-completion on endpoint paths (such as file or directory names, message queue names, database table names) when creating or using new endpoints</li><li>Reduced stack-frames in use during routing, that also makes Camel's stack traces being logged much less verbose. This also allows people to easier debug the internals of Camel as less <tt>AsyncCallback</tt> callbacks are in use during routing.</li><li>Easy to use <a shape="rect" href="message-history.html" title="Message History">Message History</a> out of the box. And included message history as "route stack-trace" when exceptions logged by <a shape="rect" href="error-handler.html" title="Error Handler">Error Handler</a> to make it easier for end users to spot where the exception occurred.</li><li><a shape="rect" href="spring-web-services.html" title="Spring Web Services">Spring Web Services</a> now supports setting/receiving SOAP headers more easily using a header on the Camel <a shape="rect" href="message.html" title="Message">Message</a>.</li><li>Evaluating <a shape="rect" href="groovy.html" title="Groovy">Groovy</a> expressions is faster as we cache the compiled scripts.</li><li>Added <tt>base64</tt> option to <a shape="rect" href="shiro-security.html" title="Shiro Security">Shiro Security</a> to allow transferring security token over <a shape="rect" href="jms.html" title="JMS">JMS</a> and other transports as base64 encoded representation.</li><li>Made it easier to use <a shape="rect" href="shiro-security.html" title="Shiro Security">Shiro Security</a> as the credentials can be provided in headers, when sending a message to a secured route.</li><li><a shape="rect" href="bindy.html" title="Bindy">Bindy</a> now supports enums.</li><l i>Added new <a shape="rect" href="backlogdebugger.html" title="BacklogDebugger">BacklogDebugger</a> to perform live debugging of messages during routing. The <a shape="rect" href="backlogdebugger.html" title="BacklogDebugger">BacklogDebugger</a> has JMX API allows tooling to control the debugger.</li><li>While using the <a shape="rect" class="external-link" href="http://xircles.codehaus.org/projects/jackson"; rel="nofollow">Jackson library</a> through the <a shape="rect" href="json.html" title="JSON">JSON</a> Dataformat there's now a <tt>jsonView</tt> attribute you could make use of directly inside the <a shape="rect" href="dsl.html" title="DSL">DSL</a> itself.</li><li><a shape="rect" href="smpp.html" title="SMPP">SMPP</a> now supports optional parameters in all commands where they are possible.</li><li><a shape="rect" href="jdbc.html" title="JDBC">JDBC</a> now supports named parameters.</li><li>Added timeout support for <a shape="rect" href="direct.html" title="Direct">Direc t</a> producers to wait for consumer to become active.</li><li>Added <tt>stats</tt> action to <a shape="rect" href="controlbus.html" title="ControlBus">ControlBus</a> to easily get performance statics in a single XML message.</li><li>Added support for request timeout on <a shape="rect" href="netty.html" title="Netty">Netty</a> producer, and to configure logging level on <a shape="rect" href="netty.html" title="Netty">Netty</a> consumer to be less noisy for ChannelClosedException which can flood the logs when client disconnects abruptly.</li><li><a shape="rect" href="springbatch.html" title="SpringBatch">Spring Batch</a> component producer now returns the <tt>JobExecution</tt> instance as the output message. Users can use the <tt>JobExecution</tt> instance to perform some operations using the Spring Batch API directly.</li><li>Added support for NULL values in <a shape="rect" href="sql-component.html" title="SQL Component">SQL</a> with named parameters.</li><li>Optimized <a sh ape="rect" href="jetty.html" title="Jetty">Jetty</a> streaming responses in non-chunked mode; and as well using buffer sizes based on <tt>HttpServletResponse.getBufferSize()</tt> instead of fixed size of 4kb.</li><li>Added <tt>greedy</tt> option to <a shape="rect" href="polling-consumer.html" title="Polling Consumer">scheduled polling consumer</a>.</li><li>Added support for accessing the length field on Java arrays in <a shape="rect" href="simple.html" title="Simple">Simple</a> language.</li><li>Added support for using JAXB annotations with Camel's Jackson <a shape="rect" href="json.html" title="JSON">JSON</a> component.</li></ul> <h3><a shape="rect" name="Camel2.12.0Release-FixedIssues"></a>Fixed Issues</h3> Modified: websites/production/camel/content/simple.html ============================================================================== --- websites/production/camel/content/simple.html (original) +++ websites/production/camel/content/simple.html Tue Jun 25 09:18:47 2013 @@ -35,6 +35,18 @@ </style> <![endif]--> + + <link href='http://camel.apache.org/styles/highlighter/styles/shCore.css' rel='stylesheet' type='text/css' /> + <link href='http://camel.apache.org/styles/highlighter/styles/shThemeEclipse.css' rel='stylesheet' type='text/css' /> + <script src='http://camel.apache.org/styles/highlighter/scripts/shCore.js' type='text/javascript'></script> + <script src='http://camel.apache.org/styles/highlighter/scripts/shBrushJava.js' type='text/javascript'></script> + <script src='http://camel.apache.org/styles/highlighter/scripts/shBrushXml.js' type='text/javascript'></script> + + <script type="text/javascript"> + SyntaxHighlighter.defaults['toolbar'] = false; + SyntaxHighlighter.all(); + </script> + <title> Apache Camel: Simple </title> @@ -52,8 +64,8 @@ <div class="content_r"> <div> <!-- Banner --> -<div id="banner-content"> - <div id="asf_logo"> +<div id="banner-content"><p> + </p><div id="asf_logo"> <div id="activemq_logo" style="height:108px; background:transparent url(banner.data/apache-camel-7.png) no-repeat scroll left top;"> <a shape="rect" style="float:left; width:310px;display:block;text-indent:-5000px;text-decoration:none;line-height:140px; margin-top:20px; margin-left:18px;" href="http://camel.apache.org/";>Camel</a> <a shape="rect" style="float:right; width:180px;display:block;text-indent:-5000px;text-decoration:none;line-height:80px; margin-top:45px; margin-right:10px;" href="http://www.apache.org";>Apache</a> @@ -113,100 +125,120 @@ From <b>Camel 2.9</b> onwards you can ne <h3><a shape="rect" name="Simple-OGNLexpressionsupport"></a>OGNL expression support</h3> <p><b>Available as of Camel 2.3</b></p> +<div class="panelMacro"><table class="infoMacro"><colgroup span="1"><col span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif"; width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1">Camel's OGNL support is for invoking methods only. You cannot access fields.<br clear="none"> +From <b>Camel 2.11.1</b> onwards we added special support for accessing the length field of Java arrays.</td></tr></table></div> + <p>The <a shape="rect" href="simple.html" title="Simple">Simple</a> and <a shape="rect" href="bean.html" title="Bean">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 <tt>getAddress()</tt> method.</p> <p>Then you can use Camel OGNL notation to access the address object:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java"> -simple(<span class="code-quote">"${body.address}"</span>) -simple(<span class="code-quote">"${body.address.street}"</span>) -simple(<span class="code-quote">"${body.address.zip}"</span>) -</pre> +<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" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java"> -simple(<span class="code-quote">"${body.address}"</span>) -simple(<span class="code-quote">"${body.getAddress.getStreet}"</span>) -simple(<span class="code-quote">"${body.address.getZip}"</span>) -simple(<span class="code-quote">"${body.doSomething}"</span>) -</pre> +<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 (<tt>?.</tt>) to avoid NPE if for example the body does NOT have an address</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java"> -simple(<span class="code-quote">"${body?.address?.street}"</span>) -</pre> +<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 <tt>Map</tt> or <tt>List</tt> types, so you can do:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java"> -simple(<span class="code-quote">"${body[foo].name}"</span>) -</pre> +<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[ +simple("${body[foo].name}") +]]></script> </div></div> <p>To assume the body is <tt>Map</tt> based and lookup the value with <tt>foo</tt> as key, and invoke the <tt>getName</tt> method on that value.</p> <div class="panelMacro"><table class="infoMacro"><colgroup span="1"><col span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif"; width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1">If the key has space, then you <b>must</b> enclose the key with quotes, for example 'foo bar': <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java"> -simple(<span class="code-quote">"${body['foo bar'].name}"</span>) -</pre> +<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[ +simple("${body['foo bar'].name}") +]]></script> </div></div></td></tr></table></div> <p>You can access the <tt>Map</tt> or <tt>List</tt> objects directly using their key name (with or without dots) :</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java"> -simple(<span class="code-quote">"${body[foo]}"</span>) -simple(<span class="code-quote">"${body[<span class="code-keyword">this</span>.is.foo]}"</span>) -</pre> +<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 <tt>foo</tt> then you can use the null safe operator to avoid the NPE as shown:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java"> -simple(<span class="code-quote">"${body[foo]?.name}"</span>) -</pre> +<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[ +simple("${body[foo]?.name}") +]]></script> </div></div> <p>You can also access <tt>List</tt> types, for example to get lines from the address you can do:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java"> -simple(<span class="code-quote">"${body.address.lines[0]}"</span>) -simple(<span class="code-quote">"${body.address.lines[1]}"</span>) -simple(<span class="code-quote">"${body.address.lines[2]}"</span>) -</pre> +<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 <tt>last</tt> keyword which can be used to get the last value from a list.</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java"> -simple(<span class="code-quote">"${body.address.lines[last]}"</span>) -</pre> +<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 <tt>last-1</tt> to indicate this:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java"> -simple(<span class="code-quote">"${body.address.lines[last-1]}"</span>) -</pre> +<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" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java"> -simple(<span class="code-quote">"${body.address.lines[last-2]}"</span>) -</pre> +<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" style="border-width: 1px;"><div class="codeContent panelContent"> +<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[ +simple("${body.address.lines.size}") +]]></script> +</div></div> + +<p>From <b>Camel 2.11.1</b> onwards we added support for the length field for Java arrays as well, eg:</p> +<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> +<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" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java"> -simple(<span class="code-quote">"${body.address.zip} > 1000"</span>) -</pre> +<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[ +simple("${body.address.zip} > 1000") +]]></script> </div></div> <h3><a shape="rect" name="Simple-Operatorsupport"></a>Operator support</h3> @@ -214,9 +246,9 @@ simple(<span class="code-quote">"${body. <p>To enable it the left value must be enclosed in ${ }. The syntax is:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java"> +<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[ ${leftValue} OP rightValue -</pre> +]]></script> </div></div> <p>Where the <tt>rightValue</tt> can be a String literal enclosed in <tt>' '</tt>, <tt>null</tt>, a constant value or another expression enclosed in ${ }.</p> @@ -247,132 +279,132 @@ ${leftValue} OP rightValue <p>The syntax for AND is:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java"> +<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[ ${leftValue} OP rightValue and ${leftValue} OP rightValue -</pre> +]]></script> </div></div> <p>And the syntax for OR is:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java"> +<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[ ${leftValue} OP rightValue or ${leftValue} OP rightValue -</pre> +]]></script> </div></div> <p>Some examples:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java"> -simple(<span class="code-quote">"${in.header.foo} == 'foo'"</span>) +<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[ +simple("${in.header.foo} == 'foo'") -<span class="code-comment">// here Camel will type convert '100' into the type of in.header.bar and <span class="code-keyword">if</span> its an <span class="code-object">Integer</span> '100' will also be converter to an <span class="code-object">Integer</span> -</span>simple(<span class="code-quote">"${in.header.bar} == '100'"</span>) +// 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'") -simple(<span class="code-quote">"${in.header.bar} == 100"</span>) +simple("${in.header.bar} == 100") -<span class="code-comment">// 100 will be converter to the type of in.header.bar so we can <span class="code-keyword">do</span> > comparison -</span>simple(<span class="code-quote">"${in.header.bar} > 100"</span>) -</pre> +// 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="panelMacro"><table class="infoMacro"><colgroup span="1"><col span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif"; width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1"><b>Comparing with different types</b><br clear="none">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: <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java"> -simple(<span class="code-quote">"100 < ${in.header.bar}"</span>) -</pre> +<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></td></tr></table></div> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java"> -<span class="code-comment">// testing <span class="code-keyword">for</span> <span class="code-keyword">null</span> -</span>simple(<span class="code-quote">"${in.header.baz} == <span class="code-keyword">null</span>"</span>) - -<span class="code-comment">// testing <span class="code-keyword">for</span> not <span class="code-keyword">null</span> -</span>simple(<span class="code-quote">"${in.header.baz} != <span class="code-keyword">null</span>"</span>) -</pre> +<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" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java"> -simple(<span class="code-quote">"${in.header.date} == ${date:now:yyyyMMdd}"</span>) +<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[ +simple("${in.header.date} == ${date:now:yyyyMMdd}") -simple(<span class="code-quote">"${in.header.type} == ${bean:orderService?method=getOrderType}"</span>) -</pre> +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" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java"> -simple(<span class="code-quote">"${in.header.title} contains 'Camel'"</span>) -</pre> +<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" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java"> -simple(<span class="code-quote">"${in.header.number} regex '\\d{4}'"</span>) -</pre> +<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" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java"> -simple(<span class="code-quote">"${in.header.type} in 'gold,silver'"</span>) -</pre> +<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" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java"> -simple(<span class="code-quote">"${in.header.type} not in 'gold,silver'"</span>) -</pre> +<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" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java"> -simple(<span class="code-quote">"${in.header.type} is 'java.lang.<span class="code-object">String</span>'"</span>) -</pre> +<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 <tt>java.lang</tt> types so you can write it as:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java"> -simple(<span class="code-quote">"${in.header.type} is '<span class="code-object">String</span>'"</span>) -</pre> +<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" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java"> -simple(<span class="code-quote">"${in.header.number} range 100..199"</span>) -</pre> +<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 <tt>..</tt> in the range without spaces. Its based on the same syntax as Groovy.</p> <p>From <b>Camel 2.9</b> onwards the range value must be in single quotes</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java"> -simple(<span class="code-quote">"${in.header.number} range '100..199'"</span>) -</pre> +<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[ +simple("${in.header.number} range '100..199'") +]]></script> </div></div> <div class="panelMacro"><table class="tipMacro"><colgroup span="1"><col span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif"; width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1"><b>Can be used in Spring XML</b><br clear="none">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: <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-xml"> - <span class="code-tag"><from uri=<span class="code-quote">"seda:orders"</span>></span> - <span class="code-tag"><filter></span> - <span class="code-tag"><simple></span>${in.header.type} == 'widget'<span class="code-tag"></simple></span> - <span class="code-tag"><to uri=<span class="code-quote">"bean:orderService?method=handleWidget"</span>/></span> - <span class="code-tag"></filter></span> - <span class="code-tag"></from></span> -</pre> +<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"/> + </filter> + </from> +]]></script> </div></div></td></tr></table></div> <h4><a shape="rect" name="Simple-Usingand%2For"></a>Using and / or</h4> @@ -382,104 +414,104 @@ for testing with simple operators. Now y <p>For instance:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java"> -simple(<span class="code-quote">"${in.header.title} contains 'Camel' and ${in.header.type'} == 'gold'"</span>) -</pre> +<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 <tt>or</tt> is also supported. The sample would be:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java"> -simple(<span class="code-quote">"${in.header.title} contains 'Camel' or ${in.header.type'} == 'gold'"</span>) -</pre> +<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><b>Notice:</b> Currently <tt>and</tt> or <tt>or</tt> can only be used <b>once</b> in a simple language expression. This might change in the future.<br clear="none"> So you <b>cannot</b> do:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java"> -simple(<span class="code-quote">"${in.header.title} contains 'Camel' and ${in.header.type'} == 'gold' and ${in.header.number} range 100..200"</span>) -</pre> +<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><a shape="rect" name="Simple-Samples"></a>Samples</h3> <p>In the Spring XML sample below we filter based on a header value:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-xml"> - <span class="code-tag"><from uri=<span class="code-quote">"seda:orders"</span>></span> - <span class="code-tag"><filter></span> - <span class="code-tag"><simple></span>${in.header.foo}<span class="code-tag"></simple></span> - <span class="code-tag"><to uri=<span class="code-quote">"mock:fooOrders"</span>/></span> - <span class="code-tag"></filter></span> - <span class="code-tag"></from></span> -</pre> +<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[ + <from uri="seda:orders"> + <filter> + <simple>${in.header.foo}</simple> + <to uri="mock:fooOrders"/> + </filter> + </from> +]]></script> </div></div> <p>The Simple language can be used for the predicate test above in the <a shape="rect" href="message-filter.html" title="Message Filter">Message Filter</a> pattern, where we test if the in message has a <tt>foo</tt> header (a header with the key <tt>foo</tt> exists). If the expression evaluates to <b>true</b> then the message is routed to the <tt>mock:fooOrders</tt> endpoint, otherwise its lost in the deep blue sea <img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/wink.gif"; height="20" width="20" alt="" border="0">.</p> <p>The same example in Java DSL:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java"> - from(<span class="code-quote">"seda:orders"</span>) - .filter().simple(<span class="code-quote">"${in.header.foo}"</span>).to(<span class="code-quote">"seda:fooOrders"</span>); -</pre> +<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[ + from("seda:orders") + .filter().simple("${in.header.foo}").to("seda:fooOrders"); +]]></script> </div></div> <p>You can also use the simple language for simple text concatenations such as:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java"> - from(<span class="code-quote">"direct:hello"</span>).transform().simple(<span class="code-quote">"Hello ${in.header.user} how are you?"</span>).to(<span class="code-quote">"mock:reply"</span>); -</pre> +<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[ + from("direct:hello").transform().simple("Hello ${in.header.user} how are you?").to("mock:reply"); +]]></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" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java"> - from(<span class="code-quote">"direct:hello"</span>).transform().simple(<span class="code-quote">"The today is ${date:now:yyyyMMdd} and its a great day."</span>).to(<span class="code-quote">"mock:reply"</span>); -</pre> +<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[ + from("direct:hello").transform().simple("The today is ${date:now:yyyyMMdd} and its a great day.").to("mock:reply"); +]]></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" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java"> - from(<span class="code-quote">"direct:order"</span>).transform().simple(<span class="code-quote">"OrderId: ${bean:orderIdGenerator}"</span>).to(<span class="code-quote">"mock:reply"</span>); -</pre> +<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[ + from("direct:order").transform().simple("OrderId: ${bean:orderIdGenerator}").to("mock:reply"); +]]></script> </div></div> <p>Where <tt>orderIdGenerator</tt> is the id of the bean registered in the <a shape="rect" href="registry.html" title="Registry">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 <tt>.method name</tt> such as below where we invoke the <tt>generateId</tt> method.</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java"> - from(<span class="code-quote">"direct:order"</span>).transform().simple(<span class="code-quote">"OrderId: ${bean:orderIdGenerator.generateId}"</span>).to(<span class="code-quote">"mock:reply"</span>); -</pre> +<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[ + from("direct:order").transform().simple("OrderId: ${bean:orderIdGenerator.generateId}").to("mock:reply"); +]]></script> </div></div> <p>We can use the <tt>?method=methodname</tt> option that we are familiar with the <a shape="rect" href="bean.html" title="Bean">Bean</a> component itself:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java"> - from(<span class="code-quote">"direct:order"</span>).transform().simple(<span class="code-quote">"OrderId: ${bean:orderIdGenerator?method=generateId}"</span>).to(<span class="code-quote">"mock:reply"</span>); -</pre> +<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[ + from("direct:order").transform().simple("OrderId: ${bean:orderIdGenerator?method=generateId}").to("mock:reply"); +]]></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" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-xml"> - <span class="code-tag"><transform></span> - <span class="code-tag"><simple></span>Hello ${bodyAs(String)} how are you?<span class="code-tag"></simple></span> - <span class="code-tag"></transform></span> -</pre> +<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[ + <transform> + <simple>Hello ${bodyAs(String)} how are you?</simple> + </transform> +]]></script> </div></div> <p>There are a few types which have a shorthand notation, so we can use <tt>String</tt> instead of <tt>java.lang.String</tt>. These are: <tt>byte[], String, Integer, Long</tt>. All other types must use their FQN name, e.g. <tt>org.w3c.dom.Document</tt>.</p> <p>Its also possible to lookup a value from a header <tt>Map</tt> in <b>Camel 2.3</b> onwards:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-xml"> - <span class="code-tag"><transform></span> - <span class="code-tag"><simple></span>The gold value is ${header.type[gold]}<span class="code-tag"></simple></span> - <span class="code-tag"></transform></span> -</pre> +<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[ + <transform> + <simple>The gold value is ${header.type[gold]}</simple> + </transform> +]]></script> </div></div> <p>In the code above we lookup the header with name <tt>type</tt> and regard it as a <tt>java.util.Map</tt> and we then lookup with the key <tt>gold</tt> and return the value.<br clear="none"> @@ -487,11 +519,11 @@ If the header is not convertible to Map <p>From Camel 2.9 onwards you can nest functions, such as shown below:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-xml"> -<span class="code-tag"><setHeader headerName=<span class="code-quote">"myHeader"</span>></span> - <span class="code-tag"><simple></span>${properties:${header.someKey}}<span class="code-tag"></simple></span> -<span class="code-tag"></setHeader></span> -</pre> +<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[ +<setHeader headerName="myHeader"> + <simple>${properties:${header.someKey}}</simple> +</setHeader> +]]></script> </div></div> <h4><a shape="rect" name="Simple-Referringtoconstantsorenums"></a>Referring to constants or enums</h4> @@ -499,24 +531,26 @@ If the header is not convertible to Map <p>Suppose you have an enum for customers</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java"><span class="code-keyword">public</span> <span class="code-keyword">enum</span> Customer { +<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[ +public enum Customer { GOLD, SILVER, BRONZE } -</pre> +]]></script> </div></div> <p>And in a <a shape="rect" href="content-based-router.html" title="Content Based Router">Content Based Router</a> we can use the <a shape="rect" href="simple.html" title="Simple">Simple</a> language to refer to this enum, to check the message which enum it matches.</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java">from(<span class="code-quote">"direct:start"</span>) +<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[ +from("direct:start") .choice() - .when().simple(<span class="code-quote">"${header.customer} == ${type:org.apache.camel.processor.Customer.GOLD}"</span>) - .to(<span class="code-quote">"mock:gold"</span>) - .when().simple(<span class="code-quote">"${header.customer} == ${type:org.apache.camel.processor.Customer.SILVER}"</span>) - .to(<span class="code-quote">"mock:silver"</span>) + .when().simple("${header.customer} == ${type:org.apache.camel.processor.Customer.GOLD}") + .to("mock:gold") + .when().simple("${header.customer} == ${type:org.apache.camel.processor.Customer.SILVER}") + .to("mock:silver") .otherwise() - .to(<span class="code-quote">"mock:other"</span>); -</pre> + .to("mock:other"); +]]></script> </div></div> <h3><a shape="rect" name="Simple-UsingnewlinesortabsinXMLDSLs"></a>Using new lines or tabs in XML DSLs</h3> @@ -524,11 +558,11 @@ If the header is not convertible to Map <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" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-xml"> -<span class="code-tag"><transform></span> - <span class="code-tag"><simple></span>The following text\nis on a new line<span class="code-tag"></simple></span> -<span class="code-tag"></transform></span> -</pre> +<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[ +<transform> + <simple>The following text\nis on a new line</simple> +</transform> +]]></script> </div></div> @@ -539,19 +573,19 @@ If the header is not convertible to Map <p>For example to set a header as a boolean type you can do:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java"> -.setHeader(<span class="code-quote">"cool"</span>, simple(<span class="code-quote">"<span class="code-keyword">true</span>"</span>, <span class="code-object">Boolean</span>.class)) -</pre> +<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[ +.setHeader("cool", simple("true", Boolean.class)) +]]></script> </div></div> <p>And in XML DSL</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-xml"> - <span class="code-tag"><setHeader headerName=<span class="code-quote">"cool"</span>></span> - <span class="code-tag"><span class="code-comment"><!-- use resultType to indicate that the type should be a java.lang.Boolean --></span></span> - <span class="code-tag"><simple resultType=<span class="code-quote">"java.lang.Boolean"</span>></span>true<span class="code-tag"></simple></span> - <span class="code-tag"></setHeader></span> -</pre> +<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[ + <setHeader headerName="cool"> + <!-- use resultType to indicate that the type should be a java.lang.Boolean --> + <simple resultType="java.lang.Boolean">true</simple> + </setHeader> +]]></script> </div></div> <h3><a shape="rect" name="Simple-Changingfunctionstartandendtokens"></a>Changing function start and end tokens</h3> @@ -559,13 +593,13 @@ If the header is not convertible to Map <p>You can configure the function start and end tokens - ${ } using the setters <tt>changeFunctionStartToken</tt> and <tt>changeFunctionEndToken</tt> on <tt>SimpleLanguage</tt>, using Java code. From Spring XML you can define a <bean> tag with the new changed tokens in the properties as shown below:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-xml"> - <span class="code-tag"><span class="code-comment"><!-- configure Simple to use custom prefix/suffix tokens --></span></span> - <span class="code-tag"><bean id=<span class="code-quote">"simple"</span> class=<span class="code-quote">"org.apache.camel.language.simple.SimpleLanguage"</span>></span> - <span class="code-tag"><property name=<span class="code-quote">"functionStartToken"</span> value=<span class="code-quote">"["</span>/></span> - <span class="code-tag"><property name=<span class="code-quote">"functionEndToken"</span> value=<span class="code-quote">"]"</span>/></span> - <span class="code-tag"></bean></span> -</pre> +<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[ + <!-- configure Simple to use custom prefix/suffix tokens --> + <bean id="simple" class="org.apache.camel.language.simple.SimpleLanguage"> + <property name="functionStartToken" value="["/> + <property name="functionEndToken" value="]"/> + </bean> +]]></script> </div></div> <p>In the example above we use [ ] as the changed tokens.</p> @@ -579,9 +613,9 @@ For example in an OSGi server this may a <p>You can externalize the script and have Camel load it from a resource such as <tt>"classpath:"</tt>, <tt>"file:"</tt>, or <tt>"http:"</tt>.<br clear="none"> This is done using the following syntax: <tt>"resource:scheme:location"</tt>, eg to refer to a file on the classpath you can do:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> -<pre class="code-java"> -.setHeader(<span class="code-quote">"myHeader"</span>).simple(<span class="code-quote">"resource:classpath:mysimple.txt"</span>) -</pre> +<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[ +.setHeader("myHeader").simple("resource:classpath:mysimple.txt") +]]></script> </div></div> <h3><a shape="rect" name="Simple-Dependencies"></a>Dependencies</h3> @@ -603,8 +637,8 @@ This is done using the following syntax: <h3><a shape="rect" name="Navigation-Search"></a>Search</h3> - -<form enctype="application/x-www-form-urlencoded" method="get" id="cse-search-box" action="http://www.google.com/cse";> +<p> +</p><form enctype="application/x-www-form-urlencoded" method="get" id="cse-search-box" action="http://www.google.com/cse";> <div> <input type="hidden" name="cx" value="007878419884033443453:m5nhvy4hmyq"> <input type="hidden" name="ie" value="UTF-8">
![https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif"](https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif"){kind=link}
![https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif"](https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif"){kind=link}
![https://cwiki.apache.org/confluence/images/icons/emoticons/wink.gif"](https://cwiki.apache.org/confluence/images/icons/emoticons/wink.gif"){kind=link}