Author: buildbot
Date: Wed Feb 18 07:19:31 2015
New Revision: 940556
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/beanshell.html
websites/production/camel/content/book-in-one-page.html
websites/production/camel/content/book-languages-appendix.html
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/groovy.html
websites/production/camel/content/javascript.html
websites/production/camel/content/netty-http.html
websites/production/camel/content/netty4-http.html
websites/production/camel/content/php.html
websites/production/camel/content/python.html
websites/production/camel/content/ruby.html
websites/production/camel/content/scripting-languages-context.html
websites/production/camel/content/scripting-languages.html
Modified: websites/production/camel/content/beanshell.html
==============================================================================
--- websites/production/camel/content/beanshell.html (original)
+++ websites/production/camel/content/beanshell.html Wed Feb 18 07:19:31 2015
@@ -122,7 +122,7 @@
<p>You could follow the examples above to create an <a shape="rect"
href="predicate.html">Predicate</a> in a <a shape="rect"
href="message-filter.html">Message Filter</a> or as an <a shape="rect"
href="expression.html">Expression</a> for a <a shape="rect"
href="recipient-list.html">Recipient List</a></p>
-<h3 id="BeanShell-ScriptContext">ScriptContext</h3><p>The JSR-223 scripting
languages ScriptContext is pre configured with the following attributes all set
at <code>ENGINE_SCOPE</code>:</p><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Attribute</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Value</p></th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>context</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.CamelContext</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The Camel Context ( It cannot
be used in groovy)</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><span>camelContext</span></p></td><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.CamelContext</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Th
e Camel Context</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>exchange</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.Exchange</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The current
Exchange</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>request</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.Message</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The IN
message</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>response</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.Message</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The OUT
message</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>properties</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.builder.script.PropertiesFunction</code></p></td><td
colsp
an="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.9:</strong>
Function with a <code>resolve</code> method to make it easier to use Camels <a
shape="rect" href="properties.html">Properties</a> component from scripts. See
further below for example.</p></td></tr></tbody></table></div><p>See <a
shape="rect" href="scripting-languages.html">Scripting Languages</a> for the
list of languages with explicit DSL support.</p><h3
id="BeanShell-AdditionalargumentstoScriptingEngine">Additional arguments to
ScriptingEngine</h3><p><strong>Available as of Camel 2.8</strong></p><p>You can
provide additional arguments to the <code>ScriptingEngine</code> using a header
on the Camel message with the key <code>CamelScriptArguments</code>.<br
clear="none"> See this example:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<h3 id="BeanShell-ScriptContext">ScriptContext</h3><p>The JSR-223 scripting
languages ScriptContext is pre configured with the following attributes all set
at <code>ENGINE_SCOPE</code>:</p><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Attribute</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Value</p></th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>context</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.CamelContext</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The Camel Context ( It cannot
be used in groovy)</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><span>camelContext</span></p></td><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.CamelContext</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Th
e Camel Context</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>exchange</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.Exchange</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The current
Exchange</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>request</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.Message</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The message (IN
message)</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>response</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.Message</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Deprecated</strong>:
The OUT message. The OUT message if null by default. Use IN message
instead.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>properties</p></td><td colspan="1" rowspan="1" class
="confluenceTd"><p><code>org.apache.camel.builder.script.PropertiesFunction</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.9:</strong>
Function with a <code>resolve</code> method to make it easier to use Camels <a
shape="rect" href="properties.html">Properties</a> component from scripts. See
further below for example.</p></td></tr></tbody></table></div><p>See <a
shape="rect" href="scripting-languages.html">Scripting Languages</a> for the
list of languages with explicit DSL support.</p><h3
id="BeanShell-AdditionalargumentstoScriptingEngine">Additional arguments to
ScriptingEngine</h3><p><strong>Available as of Camel 2.8</strong></p><p>You can
provide additional arguments to the <code>ScriptingEngine</code> using a header
on the Camel message with the key <code>CamelScriptArguments</code>.<br
clear="none"> See this example:</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[
public void testArgumentsExample() throws Exception {
if (!ScriptTestHelper.canRunTestOnThisPlatform()) {
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 Feb 18 07:19:31
2015
@@ -4125,11 +4125,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.rbtoc1424164650633 {padding: 0px;}
-div.rbtoc1424164650633 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1424164650633 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1424243904386 {padding: 0px;}
+div.rbtoc1424243904386 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1424243904386 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1424164650633">
+/*]]>*/</style></p><div class="toc-macro rbtoc1424243904386">
<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>
@@ -6315,11 +6315,11 @@ So we completed the last piece in the pi
<style type="text/css">/*<![CDATA[*/
-div.rbtoc1424164651004 {padding: 0px;}
-div.rbtoc1424164651004 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1424164651004 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1424243905216 {padding: 0px;}
+div.rbtoc1424243905216 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1424243905216 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style><div class="toc-macro rbtoc1424164651004">
+/*]]>*/</style><div class="toc-macro rbtoc1424243905216">
<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>
@@ -8333,7 +8333,7 @@ from("direct:a").recipientList
<p>However any <a shape="rect" class="external-link"
href="http://jcp.org/en/jsr/detail?id=223"; rel="nofollow">JSR 223</a> scripting
language can be used using the generic DSL methods.</p>
-<h3 id="BookInOnePage-ScriptContext">ScriptContext</h3><p>The JSR-223
scripting languages ScriptContext is pre configured with the following
attributes all set at <code>ENGINE_SCOPE</code>:</p><div
class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1"
rowspan="1" class="confluenceTh"><p>Attribute</p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Value</p></th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>context</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.CamelContext</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The Camel Context ( It cannot
be used in groovy)</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><span>camelContext</span></p></td><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.CamelContext</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><
p>The Camel Context</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>exchange</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.Exchange</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The current
Exchange</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>request</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.Message</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The IN
message</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>response</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.Message</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The OUT
message</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>properties</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.builder.script.PropertiesFunction</code></p></td><td
c
olspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.9:</strong>
Function with a <code>resolve</code> method to make it easier to use Camels <a
shape="rect" href="properties.html">Properties</a> component from scripts. See
further below for example.</p></td></tr></tbody></table></div><p>See <a
shape="rect" href="scripting-languages.html">Scripting Languages</a> for the
list of languages with explicit DSL support.</p><h3
id="BookInOnePage-AdditionalargumentstoScriptingEngine">Additional arguments to
ScriptingEngine</h3><p><strong>Available as of Camel 2.8</strong></p><p>You can
provide additional arguments to the <code>ScriptingEngine</code> using a header
on the Camel message with the key <code>CamelScriptArguments</code>.<br
clear="none"> See this example:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<h3 id="BookInOnePage-ScriptContext">ScriptContext</h3><p>The JSR-223
scripting languages ScriptContext is pre configured with the following
attributes all set at <code>ENGINE_SCOPE</code>:</p><div
class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1"
rowspan="1" class="confluenceTh"><p>Attribute</p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Value</p></th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>context</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.CamelContext</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The Camel Context ( It cannot
be used in groovy)</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><span>camelContext</span></p></td><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.CamelContext</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><
p>The Camel Context</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>exchange</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.Exchange</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The current
Exchange</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>request</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.Message</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The message (IN
message)</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>response</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.Message</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Deprecated</strong>:
The OUT message. The OUT message if null by default. Use IN message
instead.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>properties</p></td><td colspan="1" rowspan="1" c
lass="confluenceTd"><p><code>org.apache.camel.builder.script.PropertiesFunction</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.9:</strong>
Function with a <code>resolve</code> method to make it easier to use Camels <a
shape="rect" href="properties.html">Properties</a> component from scripts. See
further below for example.</p></td></tr></tbody></table></div><p>See <a
shape="rect" href="scripting-languages.html">Scripting Languages</a> for the
list of languages with explicit DSL support.</p><h3
id="BookInOnePage-AdditionalargumentstoScriptingEngine">Additional arguments to
ScriptingEngine</h3><p><strong>Available as of Camel 2.8</strong></p><p>You can
provide additional arguments to the <code>ScriptingEngine</code> using a header
on the Camel message with the key <code>CamelScriptArguments</code>.<br
clear="none"> See this example:</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[
public void testArgumentsExample() throws Exception {
if (!ScriptTestHelper.canRunTestOnThisPlatform()) {
@@ -8418,7 +8418,7 @@ result = body * 2 + 1
<p>You could follow the examples above to create an <a shape="rect"
href="predicate.html">Predicate</a> in a <a shape="rect"
href="message-filter.html">Message Filter</a> or as an <a shape="rect"
href="expression.html">Expression</a> for a <a shape="rect"
href="recipient-list.html">Recipient List</a></p>
-<h3 id="BookInOnePage-ScriptContext.1">ScriptContext</h3><p>The JSR-223
scripting languages ScriptContext is pre configured with the following
attributes all set at <code>ENGINE_SCOPE</code>:</p><div
class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1"
rowspan="1" class="confluenceTh"><p>Attribute</p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Value</p></th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>context</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.CamelContext</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The Camel Context ( It cannot
be used in groovy)</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><span>camelContext</span></p></td><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.CamelContext</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"
><p>The Camel Context</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p>exchange</p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p><code>org.apache.camel.Exchange</code></p></td><td
>colspan="1" rowspan="1" class="confluenceTd"><p>The current
>Exchange</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p>request</p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p><code>org.apache.camel.Message</code></p></td><td
>colspan="1" rowspan="1" class="confluenceTd"><p>The IN
>message</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p>response</p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p><code>org.apache.camel.Message</code></p></td><td
>colspan="1" rowspan="1" class="confluenceTd"><p>The OUT
>message</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p>properties</p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p><code>org.apache.camel.builder.script.PropertiesFunction</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.9:</strong>
Function with a <code>resolve</code> method to make it easier to use Camels <a
shape="rect" href="properties.html">Properties</a> component from scripts. See
further below for example.</p></td></tr></tbody></table></div><p>See <a
shape="rect" href="scripting-languages.html">Scripting Languages</a> for the
list of languages with explicit DSL support.</p><h3
id="BookInOnePage-AdditionalargumentstoScriptingEngine.1">Additional arguments
to ScriptingEngine</h3><p><strong>Available as of Camel 2.8</strong></p><p>You
can provide additional arguments to the <code>ScriptingEngine</code> using a
header on the Camel message with the key <code>CamelScriptArguments</code>.<br
clear="none"> See this example:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<h3 id="BookInOnePage-ScriptContext.1">ScriptContext</h3><p>The JSR-223
scripting languages ScriptContext is pre configured with the following
attributes all set at <code>ENGINE_SCOPE</code>:</p><div
class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1"
rowspan="1" class="confluenceTh"><p>Attribute</p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Value</p></th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>context</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.CamelContext</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The Camel Context ( It cannot
be used in groovy)</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><span>camelContext</span></p></td><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.CamelContext</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"
><p>The Camel Context</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p>exchange</p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p><code>org.apache.camel.Exchange</code></p></td><td
>colspan="1" rowspan="1" class="confluenceTd"><p>The current
>Exchange</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p>request</p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p><code>org.apache.camel.Message</code></p></td><td
>colspan="1" rowspan="1" class="confluenceTd"><p>The message (IN
>message)</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p>response</p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p><code>org.apache.camel.Message</code></p></td><td
>colspan="1" rowspan="1" class="confluenceTd"><p><strong>Deprecated</strong>:
>The OUT message. The OUT message if null by default. Use IN message
>instead.</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p>properties</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.builder.script.PropertiesFunction</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.9:</strong>
Function with a <code>resolve</code> method to make it easier to use Camels <a
shape="rect" href="properties.html">Properties</a> component from scripts. See
further below for example.</p></td></tr></tbody></table></div><p>See <a
shape="rect" href="scripting-languages.html">Scripting Languages</a> for the
list of languages with explicit DSL support.</p><h3
id="BookInOnePage-AdditionalargumentstoScriptingEngine.1">Additional arguments
to ScriptingEngine</h3><p><strong>Available as of Camel 2.8</strong></p><p>You
can provide additional arguments to the <code>ScriptingEngine</code> using a
header on the Camel message with the key <code>CamelScriptArguments</code>.<br
clear="none"> See this example:</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[
public void testArgumentsExample() throws Exception {
if (!ScriptTestHelper.canRunTestOnThisPlatform()) {
@@ -8506,7 +8506,7 @@ result = body * 2 + 1
]]></script>
</div></div>
-<h3 id="BookInOnePage-ScriptContext.2">ScriptContext</h3><p>The JSR-223
scripting languages ScriptContext is pre configured with the following
attributes all set at <code>ENGINE_SCOPE</code>:</p><div
class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1"
rowspan="1" class="confluenceTh"><p>Attribute</p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Value</p></th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>context</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.CamelContext</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The Camel Context ( It cannot
be used in groovy)</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><span>camelContext</span></p></td><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.CamelContext</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"
><p>The Camel Context</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p>exchange</p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p><code>org.apache.camel.Exchange</code></p></td><td
>colspan="1" rowspan="1" class="confluenceTd"><p>The current
>Exchange</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p>request</p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p><code>org.apache.camel.Message</code></p></td><td
>colspan="1" rowspan="1" class="confluenceTd"><p>The IN
>message</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p>response</p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p><code>org.apache.camel.Message</code></p></td><td
>colspan="1" rowspan="1" class="confluenceTd"><p>The OUT
>message</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p>properties</p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p><code>org.apache.camel.builder.script.PropertiesFunction</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.9:</strong>
Function with a <code>resolve</code> method to make it easier to use Camels <a
shape="rect" href="properties.html">Properties</a> component from scripts. See
further below for example.</p></td></tr></tbody></table></div><p>See <a
shape="rect" href="scripting-languages.html">Scripting Languages</a> for the
list of languages with explicit DSL support.</p><h3
id="BookInOnePage-AdditionalargumentstoScriptingEngine.2">Additional arguments
to ScriptingEngine</h3><p><strong>Available as of Camel 2.8</strong></p><p>You
can provide additional arguments to the <code>ScriptingEngine</code> using a
header on the Camel message with the key <code>CamelScriptArguments</code>.<br
clear="none"> See this example:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<h3 id="BookInOnePage-ScriptContext.2">ScriptContext</h3><p>The JSR-223
scripting languages ScriptContext is pre configured with the following
attributes all set at <code>ENGINE_SCOPE</code>:</p><div
class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1"
rowspan="1" class="confluenceTh"><p>Attribute</p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Value</p></th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>context</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.CamelContext</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The Camel Context ( It cannot
be used in groovy)</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><span>camelContext</span></p></td><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.CamelContext</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"
><p>The Camel Context</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p>exchange</p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p><code>org.apache.camel.Exchange</code></p></td><td
>colspan="1" rowspan="1" class="confluenceTd"><p>The current
>Exchange</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p>request</p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p><code>org.apache.camel.Message</code></p></td><td
>colspan="1" rowspan="1" class="confluenceTd"><p>The message (IN
>message)</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p>response</p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p><code>org.apache.camel.Message</code></p></td><td
>colspan="1" rowspan="1" class="confluenceTd"><p><strong>Deprecated</strong>:
>The OUT message. The OUT message if null by default. Use IN message
>instead.</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p>properties</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.builder.script.PropertiesFunction</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.9:</strong>
Function with a <code>resolve</code> method to make it easier to use Camels <a
shape="rect" href="properties.html">Properties</a> component from scripts. See
further below for example.</p></td></tr></tbody></table></div><p>See <a
shape="rect" href="scripting-languages.html">Scripting Languages</a> for the
list of languages with explicit DSL support.</p><h3
id="BookInOnePage-AdditionalargumentstoScriptingEngine.2">Additional arguments
to ScriptingEngine</h3><p><strong>Available as of Camel 2.8</strong></p><p>You
can provide additional arguments to the <code>ScriptingEngine</code> using a
header on the Camel message with the key <code>CamelScriptArguments</code>.<br
clear="none"> See this example:</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[
public void testArgumentsExample() throws Exception {
if (!ScriptTestHelper.canRunTestOnThisPlatform()) {
@@ -8578,7 +8578,7 @@ from("queue:foo").filter(groov
</filter>
</route>
]]></script>
-</div></div><p></p><h3
id="BookInOnePage-ScriptContext.3">ScriptContext</h3><p>The JSR-223 scripting
languages ScriptContext is pre configured with the following attributes all set
at <code>ENGINE_SCOPE</code>:</p><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Attribute</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Value</p></th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>context</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.CamelContext</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The Camel Context ( It cannot
be used in groovy)</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><span>camelContext</span></p></td><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.CamelContext</code></p></td><td
colspan="1" rowspan="1" c
lass="confluenceTd"><p>The Camel Context</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>exchange</p></td><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.Exchange</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The current
Exchange</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>request</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.Message</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The IN
message</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>response</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.Message</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The OUT
message</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>properties</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.builder.script.PropertiesFunction
</code></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><strong>Camel 2.9:</strong> Function with a
<code>resolve</code> method to make it easier to use Camels <a shape="rect"
href="properties.html">Properties</a> component from scripts. See further below
for example.</p></td></tr></tbody></table></div><p>See <a shape="rect"
href="scripting-languages.html">Scripting Languages</a> for the list of
languages with explicit DSL support.</p><h3
id="BookInOnePage-AdditionalargumentstoScriptingEngine.3">Additional arguments
to ScriptingEngine</h3><p><strong>Available as of Camel 2.8</strong></p><p>You
can provide additional arguments to the <code>ScriptingEngine</code> using a
header on the Camel message with the key <code>CamelScriptArguments</code>.<br
clear="none"> See this example:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p></p><h3
id="BookInOnePage-ScriptContext.3">ScriptContext</h3><p>The JSR-223 scripting
languages ScriptContext is pre configured with the following attributes all set
at <code>ENGINE_SCOPE</code>:</p><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Attribute</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Value</p></th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>context</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.CamelContext</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The Camel Context ( It cannot
be used in groovy)</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><span>camelContext</span></p></td><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.CamelContext</code></p></td><td
colspan="1" rowspan="1" c
lass="confluenceTd"><p>The Camel Context</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>exchange</p></td><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.Exchange</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The current
Exchange</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>request</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.Message</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The message (IN
message)</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>response</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.Message</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Deprecated</strong>:
The OUT message. The OUT message if null by default. Use IN message
instead.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>properties</p></td><td cols
pan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.builder.script.PropertiesFunction</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.9:</strong>
Function with a <code>resolve</code> method to make it easier to use Camels <a
shape="rect" href="properties.html">Properties</a> component from scripts. See
further below for example.</p></td></tr></tbody></table></div><p>See <a
shape="rect" href="scripting-languages.html">Scripting Languages</a> for the
list of languages with explicit DSL support.</p><h3
id="BookInOnePage-AdditionalargumentstoScriptingEngine.3">Additional arguments
to ScriptingEngine</h3><p><strong>Available as of Camel 2.8</strong></p><p>You
can provide additional arguments to the <code>ScriptingEngine</code> using a
header on the Camel message with the key <code>CamelScriptArguments</code>.<br
clear="none"> See this example:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent p
dl">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
public void testArgumentsExample() throws Exception {
if (!ScriptTestHelper.canRunTestOnThisPlatform()) {
@@ -8646,7 +8646,7 @@ result = body * 2 + 1
</choice>
</route>
]]></script>
-</div></div><p></p><h3
id="BookInOnePage-ScriptContext.4">ScriptContext</h3><p>The JSR-223 scripting
languages ScriptContext is pre configured with the following attributes all set
at <code>ENGINE_SCOPE</code>:</p><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Attribute</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Value</p></th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>context</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.CamelContext</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The Camel Context ( It cannot
be used in groovy)</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><span>camelContext</span></p></td><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.CamelContext</code></p></td><td
colspan="1" rowspan="1" c
lass="confluenceTd"><p>The Camel Context</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>exchange</p></td><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.Exchange</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The current
Exchange</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>request</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.Message</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The IN
message</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>response</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.Message</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The OUT
message</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>properties</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.builder.script.PropertiesFunction
</code></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><strong>Camel 2.9:</strong> Function with a
<code>resolve</code> method to make it easier to use Camels <a shape="rect"
href="properties.html">Properties</a> component from scripts. See further below
for example.</p></td></tr></tbody></table></div><p>See <a shape="rect"
href="scripting-languages.html">Scripting Languages</a> for the list of
languages with explicit DSL support.</p><h3
id="BookInOnePage-AdditionalargumentstoScriptingEngine.4">Additional arguments
to ScriptingEngine</h3><p><strong>Available as of Camel 2.8</strong></p><p>You
can provide additional arguments to the <code>ScriptingEngine</code> using a
header on the Camel message with the key <code>CamelScriptArguments</code>.<br
clear="none"> See this example:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p></p><h3
id="BookInOnePage-ScriptContext.4">ScriptContext</h3><p>The JSR-223 scripting
languages ScriptContext is pre configured with the following attributes all set
at <code>ENGINE_SCOPE</code>:</p><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Attribute</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Value</p></th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>context</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.CamelContext</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The Camel Context ( It cannot
be used in groovy)</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><span>camelContext</span></p></td><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.CamelContext</code></p></td><td
colspan="1" rowspan="1" c
lass="confluenceTd"><p>The Camel Context</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>exchange</p></td><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.Exchange</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The current
Exchange</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>request</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.Message</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The message (IN
message)</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>response</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.Message</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Deprecated</strong>:
The OUT message. The OUT message if null by default. Use IN message
instead.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>properties</p></td><td cols
pan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.builder.script.PropertiesFunction</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.9:</strong>
Function with a <code>resolve</code> method to make it easier to use Camels <a
shape="rect" href="properties.html">Properties</a> component from scripts. See
further below for example.</p></td></tr></tbody></table></div><p>See <a
shape="rect" href="scripting-languages.html">Scripting Languages</a> for the
list of languages with explicit DSL support.</p><h3
id="BookInOnePage-AdditionalargumentstoScriptingEngine.4">Additional arguments
to ScriptingEngine</h3><p><strong>Available as of Camel 2.8</strong></p><p>You
can provide additional arguments to the <code>ScriptingEngine</code> using a
header on the Camel message with the key <code>CamelScriptArguments</code>.<br
clear="none"> See this example:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent p
dl">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
public void testArgumentsExample() throws Exception {
if (!ScriptTestHelper.canRunTestOnThisPlatform()) {
@@ -8704,7 +8704,7 @@ result = body * 2 + 1
<p>For example you could use the <strong>php</strong> function to create an <a
shape="rect" href="predicate.html">Predicate</a> in a <a shape="rect"
href="message-filter.html">Message Filter</a> or as an <a shape="rect"
href="expression.html">Expression</a> for a <a shape="rect"
href="recipient-list.html">Recipient List</a></p>
-<h3 id="BookInOnePage-ScriptContext.5">ScriptContext</h3><p>The JSR-223
scripting languages ScriptContext is pre configured with the following
attributes all set at <code>ENGINE_SCOPE</code>:</p><div
class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1"
rowspan="1" class="confluenceTh"><p>Attribute</p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Value</p></th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>context</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.CamelContext</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The Camel Context ( It cannot
be used in groovy)</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><span>camelContext</span></p></td><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.CamelContext</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"
><p>The Camel Context</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p>exchange</p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p><code>org.apache.camel.Exchange</code></p></td><td
>colspan="1" rowspan="1" class="confluenceTd"><p>The current
>Exchange</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p>request</p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p><code>org.apache.camel.Message</code></p></td><td
>colspan="1" rowspan="1" class="confluenceTd"><p>The IN
>message</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p>response</p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p><code>org.apache.camel.Message</code></p></td><td
>colspan="1" rowspan="1" class="confluenceTd"><p>The OUT
>message</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p>properties</p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p><code>org.apache.camel.builder.script.PropertiesFunction</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.9:</strong>
Function with a <code>resolve</code> method to make it easier to use Camels <a
shape="rect" href="properties.html">Properties</a> component from scripts. See
further below for example.</p></td></tr></tbody></table></div><p>See <a
shape="rect" href="scripting-languages.html">Scripting Languages</a> for the
list of languages with explicit DSL support.</p><h3
id="BookInOnePage-AdditionalargumentstoScriptingEngine.5">Additional arguments
to ScriptingEngine</h3><p><strong>Available as of Camel 2.8</strong></p><p>You
can provide additional arguments to the <code>ScriptingEngine</code> using a
header on the Camel message with the key <code>CamelScriptArguments</code>.<br
clear="none"> See this example:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<h3 id="BookInOnePage-ScriptContext.5">ScriptContext</h3><p>The JSR-223
scripting languages ScriptContext is pre configured with the following
attributes all set at <code>ENGINE_SCOPE</code>:</p><div
class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1"
rowspan="1" class="confluenceTh"><p>Attribute</p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Value</p></th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>context</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.CamelContext</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The Camel Context ( It cannot
be used in groovy)</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><span>camelContext</span></p></td><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.CamelContext</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"
><p>The Camel Context</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p>exchange</p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p><code>org.apache.camel.Exchange</code></p></td><td
>colspan="1" rowspan="1" class="confluenceTd"><p>The current
>Exchange</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p>request</p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p><code>org.apache.camel.Message</code></p></td><td
>colspan="1" rowspan="1" class="confluenceTd"><p>The message (IN
>message)</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p>response</p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p><code>org.apache.camel.Message</code></p></td><td
>colspan="1" rowspan="1" class="confluenceTd"><p><strong>Deprecated</strong>:
>The OUT message. The OUT message if null by default. Use IN message
>instead.</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p>properties</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.builder.script.PropertiesFunction</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.9:</strong>
Function with a <code>resolve</code> method to make it easier to use Camels <a
shape="rect" href="properties.html">Properties</a> component from scripts. See
further below for example.</p></td></tr></tbody></table></div><p>See <a
shape="rect" href="scripting-languages.html">Scripting Languages</a> for the
list of languages with explicit DSL support.</p><h3
id="BookInOnePage-AdditionalargumentstoScriptingEngine.5">Additional arguments
to ScriptingEngine</h3><p><strong>Available as of Camel 2.8</strong></p><p>You
can provide additional arguments to the <code>ScriptingEngine</code> using a
header on the Camel message with the key <code>CamelScriptArguments</code>.<br
clear="none"> See this example:</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[
public void testArgumentsExample() throws Exception {
if (!ScriptTestHelper.canRunTestOnThisPlatform()) {
@@ -8792,7 +8792,7 @@ result = body * 2 + 1
]]></script>
</div></div>
-<h3 id="BookInOnePage-ScriptContext.6">ScriptContext</h3><p>The JSR-223
scripting languages ScriptContext is pre configured with the following
attributes all set at <code>ENGINE_SCOPE</code>:</p><div
class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1"
rowspan="1" class="confluenceTh"><p>Attribute</p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Value</p></th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>context</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.CamelContext</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The Camel Context ( It cannot
be used in groovy)</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><span>camelContext</span></p></td><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.CamelContext</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"
><p>The Camel Context</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p>exchange</p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p><code>org.apache.camel.Exchange</code></p></td><td
>colspan="1" rowspan="1" class="confluenceTd"><p>The current
>Exchange</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p>request</p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p><code>org.apache.camel.Message</code></p></td><td
>colspan="1" rowspan="1" class="confluenceTd"><p>The IN
>message</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p>response</p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p><code>org.apache.camel.Message</code></p></td><td
>colspan="1" rowspan="1" class="confluenceTd"><p>The OUT
>message</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p>properties</p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p><code>org.apache.camel.builder.script.PropertiesFunction</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.9:</strong>
Function with a <code>resolve</code> method to make it easier to use Camels <a
shape="rect" href="properties.html">Properties</a> component from scripts. See
further below for example.</p></td></tr></tbody></table></div><p>See <a
shape="rect" href="scripting-languages.html">Scripting Languages</a> for the
list of languages with explicit DSL support.</p><h3
id="BookInOnePage-AdditionalargumentstoScriptingEngine.6">Additional arguments
to ScriptingEngine</h3><p><strong>Available as of Camel 2.8</strong></p><p>You
can provide additional arguments to the <code>ScriptingEngine</code> using a
header on the Camel message with the key <code>CamelScriptArguments</code>.<br
clear="none"> See this example:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<h3 id="BookInOnePage-ScriptContext.6">ScriptContext</h3><p>The JSR-223
scripting languages ScriptContext is pre configured with the following
attributes all set at <code>ENGINE_SCOPE</code>:</p><div
class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1"
rowspan="1" class="confluenceTh"><p>Attribute</p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Value</p></th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>context</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.CamelContext</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The Camel Context ( It cannot
be used in groovy)</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><span>camelContext</span></p></td><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.CamelContext</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"
><p>The Camel Context</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p>exchange</p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p><code>org.apache.camel.Exchange</code></p></td><td
>colspan="1" rowspan="1" class="confluenceTd"><p>The current
>Exchange</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p>request</p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p><code>org.apache.camel.Message</code></p></td><td
>colspan="1" rowspan="1" class="confluenceTd"><p>The message (IN
>message)</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p>response</p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p><code>org.apache.camel.Message</code></p></td><td
>colspan="1" rowspan="1" class="confluenceTd"><p><strong>Deprecated</strong>:
>The OUT message. The OUT message if null by default. Use IN message
>instead.</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p>properties</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>org.apache.camel.builder.script.PropertiesFunction</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.9:</strong>
Function with a <code>resolve</code> method to make it easier to use Camels <a
shape="rect" href="properties.html">Properties</a> component from scripts. See
further below for example.</p></td></tr></tbody></table></div><p>See <a
shape="rect" href="scripting-languages.html">Scripting Languages</a> for the
list of languages with explicit DSL support.</p><h3
id="BookInOnePage-AdditionalargumentstoScriptingEngine.6">Additional arguments
to ScriptingEngine</h3><p><strong>Available as of Camel 2.8</strong></p><p>You
can provide additional arguments to the <code>ScriptingEngine</code> using a
header on the Camel message with the key <code>CamelScriptArguments</code>.<br
clear="none"> See this example:</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[
public void testArgumentsExample() throws Exception {
if (!ScriptTestHelper.canRunTestOnThisPlatform()) {
@@ -18842,11 +18842,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.rbtoc1424164657086 {padding: 0px;}
-div.rbtoc1424164657086 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1424164657086 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1424243911848 {padding: 0px;}
+div.rbtoc1424243911848 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1424243911848 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1424164657086">
+/*]]>*/</style></p><div class="toc-macro rbtoc1424243911848">
<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>
