camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r923374 - in /websites/production/camel/content: book-component-appendix.html book-in-one-page.html cache/main.pageCache language.html
Date Wed, 24 Sep 2014 11:18:46 GMT
Author: buildbot
Date: Wed Sep 24 11:18:46 2014
New Revision: 923374

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/book-component-appendix.html
    websites/production/camel/content/book-in-one-page.html
    websites/production/camel/content/cache/main.pageCache
    websites/production/camel/content/language.html

Modified: websites/production/camel/content/book-component-appendix.html
==============================================================================
--- websites/production/camel/content/book-component-appendix.html (original)
+++ websites/production/camel/content/book-component-appendix.html Wed Sep 24 11:18:46 2014
@@ -1529,11 +1529,11 @@ template.send("direct:alias-verify&
                     </div>
     </div>
 <p>The <strong>cxf:</strong> component provides integration with <a shape="rect" href="http://cxf.apache.org">Apache CXF</a> for connecting to JAX-WS services hosted in CXF.</p><p><style type="text/css">/*<![CDATA[*/
-div.rbtoc1411476400748 {padding: 0px;}
-div.rbtoc1411476400748 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1411476400748 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1411557444361 {padding: 0px;}
+div.rbtoc1411557444361 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1411557444361 li {margin-left: 0px;padding-left: 0px;}
 
-/*]]>*/</style></p><div class="toc-macro rbtoc1411476400748">
+/*]]>*/</style></p><div class="toc-macro rbtoc1411557444361">
 <ul class="toc-indentation"><li><a shape="rect" href="#CXF-CXFComponent">CXF Component</a>
 <ul class="toc-indentation"><li><a shape="rect" href="#CXF-URIformat">URI format</a></li><li><a shape="rect" href="#CXF-Options">Options</a>
 <ul class="toc-indentation"><li><a shape="rect" href="#CXF-Thedescriptionsofthedataformats">The descriptions of the dataformats</a>
@@ -7278,119 +7278,54 @@ from(&quot;jt400://username:password@sys
 
 <h3 id="BookComponentAppendix-SeeAlso.35">See Also</h3>
 <ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul>
-<h2 id="BookComponentAppendix-Language">Language</h2>
-<p><strong>Available as of Camel 2.5</strong></p>
-
-<p>The language component allows you to send <a shape="rect" href="exchange.html">Exchange</a> to an endpoint which executes a script by any of the supported <a shape="rect" href="languages.html">Languages</a> in Camel.<br clear="none">
-By having a component to execute language scripts, it allows more dynamic routing capabilities. For example by using the <a shape="rect" href="routing-slip.html">Routing Slip</a> or <a shape="rect" href="dynamic-router.html">Dynamic Router</a> EIPs you can send messages to <code>language</code> endpoints where the script is dynamic defined as well.</p>
-
-<p>This component is provided out of the box in <code>camel-core</code> and hence no additional JARs is needed. You only have to include additional Camel components if the language of choice mandates it, such as using <a shape="rect" href="groovy.html">Groovy</a> or <a shape="rect" href="javascript.html">JavaScript</a> languages.</p>
-
-<h3 id="BookComponentAppendix-URIformat.38">URI format</h3>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-language://languageName[:script][?options]
+<h2 id="BookComponentAppendix-Language">Language</h2><p><strong>Available as of Camel 2.5</strong></p><p>The language component allows you to send <a shape="rect" href="exchange.html">Exchange</a> to an endpoint which executes a script by any of the supported <a shape="rect" href="languages.html">Languages</a> in Camel.<br clear="none"> By having a component to execute language scripts, it allows more dynamic routing capabilities. For example by using the <a shape="rect" href="routing-slip.html">Routing Slip</a> or <a shape="rect" href="dynamic-router.html">Dynamic Router</a> EIPs you can send messages to <code>language</code> endpoints where the script is dynamic defined as well.</p><p>This component is provided out of the box in <code>camel-core</code> and hence no additional JARs is needed. You only have to include additional Camel components if the language of choice mandates it, such as using <a shape="rect" href="groovy.html">Groovy</a> or <a shape="rect" href="javascript.html
 ">JavaScript</a> languages.</p><h3 id="BookComponentAppendix-URIformat.38">URI format</h3><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[language://languageName[:script][?options]
 ]]></script>
-</div></div>
-
-<p>And from Camel 2.11 onwards you can refer to an external resource for the script using same notation as supported by the other <a shape="rect" href="language.html">Language</a>s in Camel</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-language://languageName:resource:scheme:location][?options]
+</div></div><p>And from Camel 2.11 onwards you can refer to an external resource for the script using same notation as supported by the other <a shape="rect" href="language.html">Language</a>s in Camel</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[language://languageName:resource:scheme:location][?options]
 ]]></script>
-</div></div>
-
-
-<h3 id="BookComponentAppendix-URIOptions.6">URI Options</h3>
-<p>The component supports the following options. </p>
-<div class="confluenceTableSmall">
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default Value </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> <code>languageName</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The name of the <a shape="rect" href="languages.html">Language</a> to use, such as <code>simple</code>, <code>groovy</code>, <code>javascript</code> etc. This option is mandatory. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>script</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <c
 ode>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The script to execute. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>transform</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>boolean</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Whether or not the result of the script should be used as the new message body. By setting to <code>false</code> the script is executed but the result of the script is discarded. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>contentCache</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>boolean</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd
 "><p> <strong>Camel 2.9:</strong> Whether to cache the script if loaded from a resource.<br clear="none">
-Note: from <strong>Camel 2.10.3</strong> a cached script can be forced to reload at runtime via JMX using the clearContentCache operation. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>cacheScript</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>boolean</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.13/2.12.2/2.11.3:</strong> Whether to cache the compiled script. Turning this option on can gain performance as the script is only compiled/created once, and reuse when processing Camel messages. But this may cause side-effects with data left from previous evaluation spills into the next, and concurrency issues as well. If the script being evaluated is idempotent then this option can be turned on. </p></td></tr></tbody></table></div>
-</div>
-
-<h3 id="BookComponentAppendix-MessageHeaders.11">Message Headers</h3>
-<p>The following message headers can be used to affect the behavior of the component</p>
-
-<div class="confluenceTableSmall">
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Header </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>CamelLanguageScript</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The script to execute provided in the header. Takes precedence over script configured on the endpoint. </p></td></tr></tbody></table></div>
-</div>
-
-<h3 id="BookComponentAppendix-Examples.9">Examples</h3>
-
-<p>For example you can use the <a shape="rect" href="simple.html">Simple</a> language to <a shape="rect" href="message-translator.html">Message Translator</a> a message:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h3 id="BookComponentAppendix-URIOptions.6">URI Options</h3><p>The component supports the following options.</p><div class="confluenceTableSmall"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default Value</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><code>languageName</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The name of the <a shape="rect" href="languages.html">Language</a> to use, such as <code>simple</code>, <code>groovy</code>, <code>javascript</code> etc. This option is mandatory.</p></td></tr
 ><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>script</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The script to execute.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>transform</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>boolean</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Whether or not the result of the script should be used as the new message body. By setting to <code>false</code> the script is executed but the result of the script is discarded.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>contentCache</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td cols
 pan="1" rowspan="1" class="confluenceTd"><p><code>boolean</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.9:</strong> Whether to cache the script if loaded from a resource.<br clear="none"> Note: from <strong>Camel 2.10.3</strong> a cached script can be forced to reload at runtime via JMX using the clearContentCache operation.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>cacheScript</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>boolean</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.13/2.12.2/2.11.3:</strong> Whether to cache the compiled script. Turning this option on can gain performance as the script is only compiled/created once, and reuse when processing Camel messages. But this may cause side-effects with data left from previous evaluation spills into the next, and concurren
 cy issues as well. If the script being evaluated is idempotent then this option can be turned on.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><code>binary</code></td><td colspan="1" rowspan="1" class="confluenceTd"><code>false</code></td><td colspan="1" rowspan="1" class="confluenceTd"><code>boolean</code></td><td colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.14.1:</strong> Whether the script is binary content. This is intended to be used for loading resources using the Constant language, such as loading binary files.</td></tr></tbody></table></div></div><h3 id="BookComponentAppendix-MessageHeaders.11">Message Headers</h3><p>The following message headers can be used to affect the behavior of the component</p><div class="confluenceTableSmall"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Header</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></t
 r><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>CamelLanguageScript</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The script to execute provided in the header. Takes precedence over script configured on the endpoint.</p></td></tr></tbody></table></div></div><h3 id="BookComponentAppendix-Examples.9">Examples</h3><p>For example you can use the <a shape="rect" href="simple.html">Simple</a> language to <a shape="rect" href="message-translator.html">Message Translator</a> a message:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
 String script = URLEncoder.encode(&quot;Hello ${body}&quot;, &quot;UTF-8&quot;);
 from(&quot;direct:start&quot;).to(&quot;language:simple:&quot; + script).to(&quot;mock:result&quot;);
 ]]></script>
-</div></div>
-
-<p>In case you want to convert the message body type you can do this as well:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>In case you want to convert the message body type you can do this as well:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
 String script = URLEncoder.encode(&quot;${mandatoryBodyAs(String)}&quot;, &quot;UTF-8&quot;);
 from(&quot;direct:start&quot;).to(&quot;language:simple:&quot; + script).to(&quot;mock:result&quot;);
 ]]></script>
-</div></div>
-
-<p>You can also use the <a shape="rect" href="groovy.html">Groovy</a> language, such as this example where the input message will by multiplied with 2:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>You can also use the <a shape="rect" href="groovy.html">Groovy</a> language, such as this example where the input message will by multiplied with 2:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
 String script = URLEncoder.encode(&quot;request.body * 2&quot;, &quot;UTF-8&quot;);
 from(&quot;direct:start&quot;).to(&quot;language:groovy:&quot; + script).to(&quot;mock:result&quot;);
 ]]></script>
-</div></div>
-
-<p>You can also provide the script as a header as shown below. Here we use <a shape="rect" href="xpath.html">XPath</a> language to extract the text from the <code>&lt;foo&gt;</code> tag.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-Object out = producer.requestBodyAndHeader(&quot;language:xpath&quot;, &quot;&lt;foo&gt;Hello World&lt;/foo&gt;&quot;, Exchange.LANGUAGE_SCRIPT, &quot;/foo/text()&quot;);
+</div></div><p>You can also provide the script as a header as shown below. Here we use <a shape="rect" href="xpath.html">XPath</a> language to extract the text from the <code>&lt;foo&gt;</code> tag.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[Object out = producer.requestBodyAndHeader(&quot;language:xpath&quot;, &quot;&lt;foo&gt;Hello World&lt;/foo&gt;&quot;, Exchange.LANGUAGE_SCRIPT, &quot;/foo/text()&quot;);
 assertEquals(&quot;Hello World&quot;, out);
 ]]></script>
-</div></div>
-
-<h3 id="BookComponentAppendix-Loadingscriptsfromresources">Loading scripts from resources</h3>
-<p><strong>Available as of Camel 2.9</strong></p>
-
-<p>You can specify a resource uri for a script to load in either the endpoint uri, or in the <code>Exchange.LANGUAGE_SCRIPT</code> header.<br clear="none">
-The uri must start with one of the following schemes: file:, classpath:, or http:</p>
-
-<p>For example to load a script from the classpath:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h3 id="BookComponentAppendix-Loadingscriptsfromresources">Loading scripts from resources</h3><p><strong>Available as of Camel 2.9</strong></p><p>You can specify a resource uri for a script to load in either the endpoint uri, or in the <code>Exchange.LANGUAGE_SCRIPT</code> header.<br clear="none"> The uri must start with one of the following schemes: file:, classpath:, or http:</p><p>For example to load a script from the classpath:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
 from(&quot;direct:start&quot;)
     // load the script from the classpath
     .to(&quot;language:simple:classpath:org/apache/camel/component/language/mysimplescript.txt&quot;)
     .to(&quot;mock:result&quot;);
 ]]></script>
-</div></div>
-
-<p>By default the script is loaded once and cached. However you can disable the <code>contentCache</code> option and have the script loaded on each evaluation.<br clear="none">
-For example if the file myscript.txt is changed on disk, then the updated script is used:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>By default the script is loaded once and cached. However you can disable the <code>contentCache</code> option and have the script loaded on each evaluation.<br clear="none"> For example if the file myscript.txt is changed on disk, then the updated script is used:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
 from(&quot;direct:start&quot;)
     // the script will be loaded on each message, as we disabled cache
     .to(&quot;language:simple:file:target/script/myscript.txt?contentCache=false&quot;)
     .to(&quot;mock:result&quot;);
 ]]></script>
-</div></div>
-
-<p>From <strong>Camel 2.11</strong> onwards you can refer to the resource similar to the other <a shape="rect" href="language.html">Language</a>s in Camel by prefixing with <code>"resource:"</code> as shown below:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>From <strong>Camel 2.11</strong> onwards you can refer to the resource similar to the other <a shape="rect" href="language.html">Language</a>s in Camel by prefixing with <code>"resource:"</code> as shown below:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
 from(&quot;direct:start&quot;)
     // load the script from the classpath
     .to(&quot;language:simple:resource:classpath:org/apache/camel/component/language/mysimplescript.txt&quot;)
     .to(&quot;mock:result&quot;);
 ]]></script>
-</div></div>
-
-
-<h3 id="BookComponentAppendix-SeeAlso.36">See Also</h3>
-<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul>
-<ul class="alternate"><li><a shape="rect" href="languages.html">Languages</a></li><li><a shape="rect" href="routing-slip.html">Routing Slip</a></li><li><a shape="rect" href="dynamic-router.html">Dynamic Router</a></li></ul>
+</div></div><p></p><h3 id="BookComponentAppendix-SeeAlso.36">See Also</h3>
+<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul><ul class="alternate"><li><a shape="rect" href="languages.html">Languages</a></li><li><a shape="rect" href="routing-slip.html">Routing Slip</a></li><li><a shape="rect" href="dynamic-router.html">Dynamic Router</a></li></ul>
 <h2 id="BookComponentAppendix-LDAPComponent">LDAP Component</h2>
 
 <p>The <strong>ldap</strong> component allows you to perform searches in LDAP servers using filters as the message payload.<br clear="none">

Modified: websites/production/camel/content/book-in-one-page.html
==============================================================================
--- websites/production/camel/content/book-in-one-page.html (original)
+++ websites/production/camel/content/book-in-one-page.html Wed Sep 24 11:18:46 2014
@@ -4122,11 +4122,11 @@ While not actual tutorials you might fin
                     </div>
     </div>
 <h2 id="BookInOnePage-Preface">Preface</h2><p>This tutorial aims to guide the reader through the stages of creating a project which uses Camel to facilitate the routing of messages from a JMS queue to a <a shape="rect" class="external-link" href="http://www.springramework.org" rel="nofollow">Spring</a> service. The route works in a synchronous fashion returning a response to the client.</p><p><style type="text/css">/*<![CDATA[*/
-div.rbtoc1411476342391 {padding: 0px;}
-div.rbtoc1411476342391 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1411476342391 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1411557456191 {padding: 0px;}
+div.rbtoc1411557456191 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1411557456191 li {margin-left: 0px;padding-left: 0px;}
 
-/*]]>*/</style></p><div class="toc-macro rbtoc1411476342391">
+/*]]>*/</style></p><div class="toc-macro rbtoc1411557456191">
 <ul class="toc-indentation"><li><a shape="rect" href="#Tutorial-JmsRemoting-TutorialonSpringRemotingwithJMS">Tutorial on Spring Remoting with JMS</a></li><li><a shape="rect" href="#Tutorial-JmsRemoting-Preface">Preface</a></li><li><a shape="rect" href="#Tutorial-JmsRemoting-Prerequisites">Prerequisites</a></li><li><a shape="rect" href="#Tutorial-JmsRemoting-Distribution">Distribution</a></li><li><a shape="rect" href="#Tutorial-JmsRemoting-About">About</a></li><li><a shape="rect" href="#Tutorial-JmsRemoting-CreatetheCamelProject">Create the Camel Project</a>
 <ul class="toc-indentation"><li><a shape="rect" href="#Tutorial-JmsRemoting-UpdatethePOMwithDependencies">Update the POM with Dependencies</a></li></ul>
 </li><li><a shape="rect" href="#Tutorial-JmsRemoting-WritingtheServer">Writing the Server</a>
@@ -6312,11 +6312,11 @@ So we completed the last piece in the pi
 
 
 <style type="text/css">/*<![CDATA[*/
-div.rbtoc1411476342886 {padding: 0px;}
-div.rbtoc1411476342886 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1411476342886 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1411557456506 {padding: 0px;}
+div.rbtoc1411557456506 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1411557456506 li {margin-left: 0px;padding-left: 0px;}
 
-/*]]>*/</style><div class="toc-macro rbtoc1411476342886">
+/*]]>*/</style><div class="toc-macro rbtoc1411557456506">
 <ul class="toc-indentation"><li><a shape="rect" href="#Tutorial-AXIS-Camel-TutorialusingAxis1.4withApacheCamel">Tutorial using Axis 1.4 with Apache Camel</a>
 <ul class="toc-indentation"><li><a shape="rect" href="#Tutorial-AXIS-Camel-Prerequisites">Prerequisites</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-Distribution">Distribution</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-Introduction">Introduction</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-SettinguptheprojecttorunAxis">Setting up the project to run Axis</a>
 <ul class="toc-indentation"><li><a shape="rect" href="#Tutorial-AXIS-Camel-Maven2">Maven 2</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-wsdl">wsdl</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-ConfiguringAxis">Configuring Axis</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-RunningtheExample">Running the Example</a></li></ul>
@@ -19769,11 +19769,11 @@ template.send(&quot;direct:alias-verify&
                     </div>
     </div>
 <p>The <strong>cxf:</strong> component provides integration with <a shape="rect" href="http://cxf.apache.org">Apache CXF</a> for connecting to JAX-WS services hosted in CXF.</p><p><style type="text/css">/*<![CDATA[*/
-div.rbtoc1411476348827 {padding: 0px;}
-div.rbtoc1411476348827 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1411476348827 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1411557466040 {padding: 0px;}
+div.rbtoc1411557466040 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1411557466040 li {margin-left: 0px;padding-left: 0px;}
 
-/*]]>*/</style></p><div class="toc-macro rbtoc1411476348827">
+/*]]>*/</style></p><div class="toc-macro rbtoc1411557466040">
 <ul class="toc-indentation"><li><a shape="rect" href="#CXF-CXFComponent">CXF Component</a>
 <ul class="toc-indentation"><li><a shape="rect" href="#CXF-URIformat">URI format</a></li><li><a shape="rect" href="#CXF-Options">Options</a>
 <ul class="toc-indentation"><li><a shape="rect" href="#CXF-Thedescriptionsofthedataformats">The descriptions of the dataformats</a>
@@ -25518,119 +25518,54 @@ from(&quot;jt400://username:password@sys
 
 <h3 id="BookInOnePage-SeeAlso.55">See Also</h3>
 <ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul>
-<h2 id="BookInOnePage-Language">Language</h2>
-<p><strong>Available as of Camel 2.5</strong></p>
-
-<p>The language component allows you to send <a shape="rect" href="exchange.html">Exchange</a> to an endpoint which executes a script by any of the supported <a shape="rect" href="languages.html">Languages</a> in Camel.<br clear="none">
-By having a component to execute language scripts, it allows more dynamic routing capabilities. For example by using the <a shape="rect" href="routing-slip.html">Routing Slip</a> or <a shape="rect" href="dynamic-router.html">Dynamic Router</a> EIPs you can send messages to <code>language</code> endpoints where the script is dynamic defined as well.</p>
-
-<p>This component is provided out of the box in <code>camel-core</code> and hence no additional JARs is needed. You only have to include additional Camel components if the language of choice mandates it, such as using <a shape="rect" href="groovy.html">Groovy</a> or <a shape="rect" href="javascript.html">JavaScript</a> languages.</p>
-
-<h3 id="BookInOnePage-URIformat.39">URI format</h3>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-language://languageName[:script][?options]
+<h2 id="BookInOnePage-Language">Language</h2><p><strong>Available as of Camel 2.5</strong></p><p>The language component allows you to send <a shape="rect" href="exchange.html">Exchange</a> to an endpoint which executes a script by any of the supported <a shape="rect" href="languages.html">Languages</a> in Camel.<br clear="none"> By having a component to execute language scripts, it allows more dynamic routing capabilities. For example by using the <a shape="rect" href="routing-slip.html">Routing Slip</a> or <a shape="rect" href="dynamic-router.html">Dynamic Router</a> EIPs you can send messages to <code>language</code> endpoints where the script is dynamic defined as well.</p><p>This component is provided out of the box in <code>camel-core</code> and hence no additional JARs is needed. You only have to include additional Camel components if the language of choice mandates it, such as using <a shape="rect" href="groovy.html">Groovy</a> or <a shape="rect" href="javascript.html">JavaSc
 ript</a> languages.</p><h3 id="BookInOnePage-URIformat.39">URI format</h3><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[language://languageName[:script][?options]
 ]]></script>
-</div></div>
-
-<p>And from Camel 2.11 onwards you can refer to an external resource for the script using same notation as supported by the other <a shape="rect" href="language.html">Language</a>s in Camel</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-language://languageName:resource:scheme:location][?options]
+</div></div><p>And from Camel 2.11 onwards you can refer to an external resource for the script using same notation as supported by the other <a shape="rect" href="language.html">Language</a>s in Camel</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[language://languageName:resource:scheme:location][?options]
 ]]></script>
-</div></div>
-
-
-<h3 id="BookInOnePage-URIOptions.6">URI Options</h3>
-<p>The component supports the following options. </p>
-<div class="confluenceTableSmall">
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default Value </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> <code>languageName</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The name of the <a shape="rect" href="languages.html">Language</a> to use, such as <code>simple</code>, <code>groovy</code>, <code>javascript</code> etc. This option is mandatory. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>script</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <c
 ode>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The script to execute. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>transform</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>boolean</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Whether or not the result of the script should be used as the new message body. By setting to <code>false</code> the script is executed but the result of the script is discarded. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>contentCache</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>boolean</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd
 "><p> <strong>Camel 2.9:</strong> Whether to cache the script if loaded from a resource.<br clear="none">
-Note: from <strong>Camel 2.10.3</strong> a cached script can be forced to reload at runtime via JMX using the clearContentCache operation. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>cacheScript</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>boolean</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.13/2.12.2/2.11.3:</strong> Whether to cache the compiled script. Turning this option on can gain performance as the script is only compiled/created once, and reuse when processing Camel messages. But this may cause side-effects with data left from previous evaluation spills into the next, and concurrency issues as well. If the script being evaluated is idempotent then this option can be turned on. </p></td></tr></tbody></table></div>
-</div>
-
-<h3 id="BookInOnePage-MessageHeaders.11">Message Headers</h3>
-<p>The following message headers can be used to affect the behavior of the component</p>
-
-<div class="confluenceTableSmall">
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Header </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>CamelLanguageScript</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The script to execute provided in the header. Takes precedence over script configured on the endpoint. </p></td></tr></tbody></table></div>
-</div>
-
-<h3 id="BookInOnePage-Examples.20">Examples</h3>
-
-<p>For example you can use the <a shape="rect" href="simple.html">Simple</a> language to <a shape="rect" href="message-translator.html">Message Translator</a> a message:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h3 id="BookInOnePage-URIOptions.6">URI Options</h3><p>The component supports the following options.</p><div class="confluenceTableSmall"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default Value</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><code>languageName</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The name of the <a shape="rect" href="languages.html">Language</a> to use, such as <code>simple</code>, <code>groovy</code>, <code>javascript</code> etc. This option is mandatory.</p></td></tr><tr><td
  colspan="1" rowspan="1" class="confluenceTd"><p><code>script</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The script to execute.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>transform</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>boolean</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Whether or not the result of the script should be used as the new message body. By setting to <code>false</code> the script is executed but the result of the script is discarded.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>contentCache</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" 
 rowspan="1" class="confluenceTd"><p><code>boolean</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.9:</strong> Whether to cache the script if loaded from a resource.<br clear="none"> Note: from <strong>Camel 2.10.3</strong> a cached script can be forced to reload at runtime via JMX using the clearContentCache operation.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>cacheScript</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>boolean</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.13/2.12.2/2.11.3:</strong> Whether to cache the compiled script. Turning this option on can gain performance as the script is only compiled/created once, and reuse when processing Camel messages. But this may cause side-effects with data left from previous evaluation spills into the next, and concurrency issue
 s as well. If the script being evaluated is idempotent then this option can be turned on.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><code>binary</code></td><td colspan="1" rowspan="1" class="confluenceTd"><code>false</code></td><td colspan="1" rowspan="1" class="confluenceTd"><code>boolean</code></td><td colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.14.1:</strong> Whether the script is binary content. This is intended to be used for loading resources using the Constant language, such as loading binary files.</td></tr></tbody></table></div></div><h3 id="BookInOnePage-MessageHeaders.11">Message Headers</h3><p>The following message headers can be used to affect the behavior of the component</p><div class="confluenceTableSmall"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Header</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspa
 n="1" rowspan="1" class="confluenceTd"><p><code>CamelLanguageScript</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The script to execute provided in the header. Takes precedence over script configured on the endpoint.</p></td></tr></tbody></table></div></div><h3 id="BookInOnePage-Examples.20">Examples</h3><p>For example you can use the <a shape="rect" href="simple.html">Simple</a> language to <a shape="rect" href="message-translator.html">Message Translator</a> a message:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
 String script = URLEncoder.encode(&quot;Hello ${body}&quot;, &quot;UTF-8&quot;);
 from(&quot;direct:start&quot;).to(&quot;language:simple:&quot; + script).to(&quot;mock:result&quot;);
 ]]></script>
-</div></div>
-
-<p>In case you want to convert the message body type you can do this as well:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>In case you want to convert the message body type you can do this as well:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
 String script = URLEncoder.encode(&quot;${mandatoryBodyAs(String)}&quot;, &quot;UTF-8&quot;);
 from(&quot;direct:start&quot;).to(&quot;language:simple:&quot; + script).to(&quot;mock:result&quot;);
 ]]></script>
-</div></div>
-
-<p>You can also use the <a shape="rect" href="groovy.html">Groovy</a> language, such as this example where the input message will by multiplied with 2:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>You can also use the <a shape="rect" href="groovy.html">Groovy</a> language, such as this example where the input message will by multiplied with 2:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
 String script = URLEncoder.encode(&quot;request.body * 2&quot;, &quot;UTF-8&quot;);
 from(&quot;direct:start&quot;).to(&quot;language:groovy:&quot; + script).to(&quot;mock:result&quot;);
 ]]></script>
-</div></div>
-
-<p>You can also provide the script as a header as shown below. Here we use <a shape="rect" href="xpath.html">XPath</a> language to extract the text from the <code>&lt;foo&gt;</code> tag.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-Object out = producer.requestBodyAndHeader(&quot;language:xpath&quot;, &quot;&lt;foo&gt;Hello World&lt;/foo&gt;&quot;, Exchange.LANGUAGE_SCRIPT, &quot;/foo/text()&quot;);
+</div></div><p>You can also provide the script as a header as shown below. Here we use <a shape="rect" href="xpath.html">XPath</a> language to extract the text from the <code>&lt;foo&gt;</code> tag.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[Object out = producer.requestBodyAndHeader(&quot;language:xpath&quot;, &quot;&lt;foo&gt;Hello World&lt;/foo&gt;&quot;, Exchange.LANGUAGE_SCRIPT, &quot;/foo/text()&quot;);
 assertEquals(&quot;Hello World&quot;, out);
 ]]></script>
-</div></div>
-
-<h3 id="BookInOnePage-Loadingscriptsfromresources">Loading scripts from resources</h3>
-<p><strong>Available as of Camel 2.9</strong></p>
-
-<p>You can specify a resource uri for a script to load in either the endpoint uri, or in the <code>Exchange.LANGUAGE_SCRIPT</code> header.<br clear="none">
-The uri must start with one of the following schemes: file:, classpath:, or http:</p>
-
-<p>For example to load a script from the classpath:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h3 id="BookInOnePage-Loadingscriptsfromresources">Loading scripts from resources</h3><p><strong>Available as of Camel 2.9</strong></p><p>You can specify a resource uri for a script to load in either the endpoint uri, or in the <code>Exchange.LANGUAGE_SCRIPT</code> header.<br clear="none"> The uri must start with one of the following schemes: file:, classpath:, or http:</p><p>For example to load a script from the classpath:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
 from(&quot;direct:start&quot;)
     // load the script from the classpath
     .to(&quot;language:simple:classpath:org/apache/camel/component/language/mysimplescript.txt&quot;)
     .to(&quot;mock:result&quot;);
 ]]></script>
-</div></div>
-
-<p>By default the script is loaded once and cached. However you can disable the <code>contentCache</code> option and have the script loaded on each evaluation.<br clear="none">
-For example if the file myscript.txt is changed on disk, then the updated script is used:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>By default the script is loaded once and cached. However you can disable the <code>contentCache</code> option and have the script loaded on each evaluation.<br clear="none"> For example if the file myscript.txt is changed on disk, then the updated script is used:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
 from(&quot;direct:start&quot;)
     // the script will be loaded on each message, as we disabled cache
     .to(&quot;language:simple:file:target/script/myscript.txt?contentCache=false&quot;)
     .to(&quot;mock:result&quot;);
 ]]></script>
-</div></div>
-
-<p>From <strong>Camel 2.11</strong> onwards you can refer to the resource similar to the other <a shape="rect" href="language.html">Language</a>s in Camel by prefixing with <code>"resource:"</code> as shown below:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>From <strong>Camel 2.11</strong> onwards you can refer to the resource similar to the other <a shape="rect" href="language.html">Language</a>s in Camel by prefixing with <code>"resource:"</code> as shown below:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
 from(&quot;direct:start&quot;)
     // load the script from the classpath
     .to(&quot;language:simple:resource:classpath:org/apache/camel/component/language/mysimplescript.txt&quot;)
     .to(&quot;mock:result&quot;);
 ]]></script>
-</div></div>
-
-
-<h3 id="BookInOnePage-SeeAlso.56">See Also</h3>
-<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul>
-<ul class="alternate"><li><a shape="rect" href="languages.html">Languages</a></li><li><a shape="rect" href="routing-slip.html">Routing Slip</a></li><li><a shape="rect" href="dynamic-router.html">Dynamic Router</a></li></ul>
+</div></div><p></p><h3 id="BookInOnePage-SeeAlso.56">See Also</h3>
+<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul><ul class="alternate"><li><a shape="rect" href="languages.html">Languages</a></li><li><a shape="rect" href="routing-slip.html">Routing Slip</a></li><li><a shape="rect" href="dynamic-router.html">Dynamic Router</a></li></ul>
 <h2 id="BookInOnePage-LDAPComponent">LDAP Component</h2>
 
 <p>The <strong>ldap</strong> component allows you to perform searches in LDAP servers using filters as the message payload.<br clear="none">

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

Modified: websites/production/camel/content/language.html
==============================================================================
--- websites/production/camel/content/language.html (original)
+++ websites/production/camel/content/language.html Wed Sep 24 11:18:46 2014
@@ -86,119 +86,54 @@
 	<tbody>
         <tr>
         <td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2 id="Language-Language">Language</h2>
-<p><strong>Available as of Camel 2.5</strong></p>
-
-<p>The language component allows you to send <a shape="rect" href="exchange.html">Exchange</a> to an endpoint which executes a script by any of the supported <a shape="rect" href="languages.html">Languages</a> in Camel.<br clear="none">
-By having a component to execute language scripts, it allows more dynamic routing capabilities. For example by using the <a shape="rect" href="routing-slip.html">Routing Slip</a> or <a shape="rect" href="dynamic-router.html">Dynamic Router</a> EIPs you can send messages to <code>language</code> endpoints where the script is dynamic defined as well.</p>
-
-<p>This component is provided out of the box in <code>camel-core</code> and hence no additional JARs is needed. You only have to include additional Camel components if the language of choice mandates it, such as using <a shape="rect" href="groovy.html">Groovy</a> or <a shape="rect" href="javascript.html">JavaScript</a> languages.</p>
-
-<h3 id="Language-URIformat">URI format</h3>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-language://languageName[:script][?options]
+<div class="wiki-content maincontent"><h2 id="Language-Language">Language</h2><p><strong>Available as of Camel 2.5</strong></p><p>The language component allows you to send <a shape="rect" href="exchange.html">Exchange</a> to an endpoint which executes a script by any of the supported <a shape="rect" href="languages.html">Languages</a> in Camel.<br clear="none"> By having a component to execute language scripts, it allows more dynamic routing capabilities. For example by using the <a shape="rect" href="routing-slip.html">Routing Slip</a> or <a shape="rect" href="dynamic-router.html">Dynamic Router</a> EIPs you can send messages to <code>language</code> endpoints where the script is dynamic defined as well.</p><p>This component is provided out of the box in <code>camel-core</code> and hence no additional JARs is needed. You only have to include additional Camel components if the language of choice mandates it, such as using <a shape="rect" href="groovy.html">Groovy</a> or <a shape="re
 ct" href="javascript.html">JavaScript</a> languages.</p><h3 id="Language-URIformat">URI format</h3><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[language://languageName[:script][?options]
 ]]></script>
-</div></div>
-
-<p>And from Camel 2.11 onwards you can refer to an external resource for the script using same notation as supported by the other <a shape="rect" href="language.html">Language</a>s in Camel</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-language://languageName:resource:scheme:location][?options]
+</div></div><p>And from Camel 2.11 onwards you can refer to an external resource for the script using same notation as supported by the other <a shape="rect" href="language.html">Language</a>s in Camel</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[language://languageName:resource:scheme:location][?options]
 ]]></script>
-</div></div>
-
-
-<h3 id="Language-URIOptions">URI Options</h3>
-<p>The component supports the following options. </p>
-<div class="confluenceTableSmall">
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default Value </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> <code>languageName</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The name of the <a shape="rect" href="languages.html">Language</a> to use, such as <code>simple</code>, <code>groovy</code>, <code>javascript</code> etc. This option is mandatory. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>script</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <c
 ode>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>String</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The script to execute. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>transform</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>boolean</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Whether or not the result of the script should be used as the new message body. By setting to <code>false</code> the script is executed but the result of the script is discarded. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>contentCache</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>boolean</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd
 "><p> <strong>Camel 2.9:</strong> Whether to cache the script if loaded from a resource.<br clear="none">
-Note: from <strong>Camel 2.10.3</strong> a cached script can be forced to reload at runtime via JMX using the clearContentCache operation. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>cacheScript</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>boolean</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.13/2.12.2/2.11.3:</strong> Whether to cache the compiled script. Turning this option on can gain performance as the script is only compiled/created once, and reuse when processing Camel messages. But this may cause side-effects with data left from previous evaluation spills into the next, and concurrency issues as well. If the script being evaluated is idempotent then this option can be turned on. </p></td></tr></tbody></table></div>
-</div>
-
-<h3 id="Language-MessageHeaders">Message Headers</h3>
-<p>The following message headers can be used to affect the behavior of the component</p>
-
-<div class="confluenceTableSmall">
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Header </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>CamelLanguageScript</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The script to execute provided in the header. Takes precedence over script configured on the endpoint. </p></td></tr></tbody></table></div>
-</div>
-
-<h3 id="Language-Examples">Examples</h3>
-
-<p>For example you can use the <a shape="rect" href="simple.html">Simple</a> language to <a shape="rect" href="message-translator.html">Message Translator</a> a message:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h3 id="Language-URIOptions">URI Options</h3><p>The component supports the following options.</p><div class="confluenceTableSmall"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default Value</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><code>languageName</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The name of the <a shape="rect" href="languages.html">Language</a> to use, such as <code>simple</code>, <code>groovy</code>, <code>javascript</code> etc. This option is mandatory.</p></td></tr><tr><td colspa
 n="1" rowspan="1" class="confluenceTd"><p><code>script</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The script to execute.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>transform</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>boolean</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Whether or not the result of the script should be used as the new message body. By setting to <code>false</code> the script is executed but the result of the script is discarded.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>contentCache</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan
 ="1" class="confluenceTd"><p><code>boolean</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.9:</strong> Whether to cache the script if loaded from a resource.<br clear="none"> Note: from <strong>Camel 2.10.3</strong> a cached script can be forced to reload at runtime via JMX using the clearContentCache operation.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>cacheScript</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>boolean</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.13/2.12.2/2.11.3:</strong> Whether to cache the compiled script. Turning this option on can gain performance as the script is only compiled/created once, and reuse when processing Camel messages. But this may cause side-effects with data left from previous evaluation spills into the next, and concurrency issues as we
 ll. If the script being evaluated is idempotent then this option can be turned on.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><code>binary</code></td><td colspan="1" rowspan="1" class="confluenceTd"><code>false</code></td><td colspan="1" rowspan="1" class="confluenceTd"><code>boolean</code></td><td colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.14.1:</strong> Whether the script is binary content. This is intended to be used for loading resources using the Constant language, such as loading binary files.</td></tr></tbody></table></div></div><h3 id="Language-MessageHeaders">Message Headers</h3><p>The following message headers can be used to affect the behavior of the component</p><div class="confluenceTableSmall"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Header</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="
 1" class="confluenceTd"><p><code>CamelLanguageScript</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The script to execute provided in the header. Takes precedence over script configured on the endpoint.</p></td></tr></tbody></table></div></div><h3 id="Language-Examples">Examples</h3><p>For example you can use the <a shape="rect" href="simple.html">Simple</a> language to <a shape="rect" href="message-translator.html">Message Translator</a> a message:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
 String script = URLEncoder.encode(&quot;Hello ${body}&quot;, &quot;UTF-8&quot;);
 from(&quot;direct:start&quot;).to(&quot;language:simple:&quot; + script).to(&quot;mock:result&quot;);
 ]]></script>
-</div></div>
-
-<p>In case you want to convert the message body type you can do this as well:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>In case you want to convert the message body type you can do this as well:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
 String script = URLEncoder.encode(&quot;${mandatoryBodyAs(String)}&quot;, &quot;UTF-8&quot;);
 from(&quot;direct:start&quot;).to(&quot;language:simple:&quot; + script).to(&quot;mock:result&quot;);
 ]]></script>
-</div></div>
-
-<p>You can also use the <a shape="rect" href="groovy.html">Groovy</a> language, such as this example where the input message will by multiplied with 2:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>You can also use the <a shape="rect" href="groovy.html">Groovy</a> language, such as this example where the input message will by multiplied with 2:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
 String script = URLEncoder.encode(&quot;request.body * 2&quot;, &quot;UTF-8&quot;);
 from(&quot;direct:start&quot;).to(&quot;language:groovy:&quot; + script).to(&quot;mock:result&quot;);
 ]]></script>
-</div></div>
-
-<p>You can also provide the script as a header as shown below. Here we use <a shape="rect" href="xpath.html">XPath</a> language to extract the text from the <code>&lt;foo&gt;</code> tag.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-Object out = producer.requestBodyAndHeader(&quot;language:xpath&quot;, &quot;&lt;foo&gt;Hello World&lt;/foo&gt;&quot;, Exchange.LANGUAGE_SCRIPT, &quot;/foo/text()&quot;);
+</div></div><p>You can also provide the script as a header as shown below. Here we use <a shape="rect" href="xpath.html">XPath</a> language to extract the text from the <code>&lt;foo&gt;</code> tag.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[Object out = producer.requestBodyAndHeader(&quot;language:xpath&quot;, &quot;&lt;foo&gt;Hello World&lt;/foo&gt;&quot;, Exchange.LANGUAGE_SCRIPT, &quot;/foo/text()&quot;);
 assertEquals(&quot;Hello World&quot;, out);
 ]]></script>
-</div></div>
-
-<h3 id="Language-Loadingscriptsfromresources">Loading scripts from resources</h3>
-<p><strong>Available as of Camel 2.9</strong></p>
-
-<p>You can specify a resource uri for a script to load in either the endpoint uri, or in the <code>Exchange.LANGUAGE_SCRIPT</code> header.<br clear="none">
-The uri must start with one of the following schemes: file:, classpath:, or http:</p>
-
-<p>For example to load a script from the classpath:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h3 id="Language-Loadingscriptsfromresources">Loading scripts from resources</h3><p><strong>Available as of Camel 2.9</strong></p><p>You can specify a resource uri for a script to load in either the endpoint uri, or in the <code>Exchange.LANGUAGE_SCRIPT</code> header.<br clear="none"> The uri must start with one of the following schemes: file:, classpath:, or http:</p><p>For example to load a script from the classpath:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
 from(&quot;direct:start&quot;)
     // load the script from the classpath
     .to(&quot;language:simple:classpath:org/apache/camel/component/language/mysimplescript.txt&quot;)
     .to(&quot;mock:result&quot;);
 ]]></script>
-</div></div>
-
-<p>By default the script is loaded once and cached. However you can disable the <code>contentCache</code> option and have the script loaded on each evaluation.<br clear="none">
-For example if the file myscript.txt is changed on disk, then the updated script is used:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>By default the script is loaded once and cached. However you can disable the <code>contentCache</code> option and have the script loaded on each evaluation.<br clear="none"> For example if the file myscript.txt is changed on disk, then the updated script is used:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
 from(&quot;direct:start&quot;)
     // the script will be loaded on each message, as we disabled cache
     .to(&quot;language:simple:file:target/script/myscript.txt?contentCache=false&quot;)
     .to(&quot;mock:result&quot;);
 ]]></script>
-</div></div>
-
-<p>From <strong>Camel 2.11</strong> onwards you can refer to the resource similar to the other <a shape="rect" href="language.html">Language</a>s in Camel by prefixing with <code>"resource:"</code> as shown below:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>From <strong>Camel 2.11</strong> onwards you can refer to the resource similar to the other <a shape="rect" href="language.html">Language</a>s in Camel by prefixing with <code>"resource:"</code> as shown below:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
 from(&quot;direct:start&quot;)
     // load the script from the classpath
     .to(&quot;language:simple:resource:classpath:org/apache/camel/component/language/mysimplescript.txt&quot;)
     .to(&quot;mock:result&quot;);
 ]]></script>
-</div></div>
-
-
-<h3 id="Language-SeeAlso">See Also</h3>
-<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul>
-<ul class="alternate"><li><a shape="rect" href="languages.html">Languages</a></li><li><a shape="rect" href="routing-slip.html">Routing Slip</a></li><li><a shape="rect" href="dynamic-router.html">Dynamic Router</a></li></ul></div>
+</div></div><p></p><h3 id="Language-SeeAlso">See Also</h3>
+<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul><ul class="alternate"><li><a shape="rect" href="languages.html">Languages</a></li><li><a shape="rect" href="routing-slip.html">Routing Slip</a></li><li><a shape="rect" href="dynamic-router.html">Dynamic Router</a></li></ul></div>
         </td>
         <td valign="top">
           <div class="navigation">



Mime
View raw message