camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r940556 [4/4] - in /websites/production/camel/content: ./ cache/
Date Wed, 18 Feb 2015 07:19:32 GMT
Modified: websites/production/camel/content/ruby.html
==============================================================================
--- websites/production/camel/content/ruby.html (original)
+++ websites/production/camel/content/ruby.html Wed Feb 18 07:19:31 2015
@@ -130,7 +130,7 @@
 ]]></script>
 </div></div>
 
-<h3 id="Ruby-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 Cam
 el 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="Ruby-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="Ruby-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 Cam
 el 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="con
 fluenceTd"><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="Ruby-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/scripting-languages-context.html
==============================================================================
--- websites/production/camel/content/scripting-languages-context.html (original)
+++ websites/production/camel/content/scripting-languages-context.html Wed Feb 18 07:19:31
2015
@@ -86,7 +86,7 @@
 	<tbody>
         <tr>
         <td valign="top" width="100%">
-<div class="wiki-content maincontent"><h3 id="ScriptingLanguagesContext-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.buil
 der.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="ScriptingLanguagesContext-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">
+<div class="wiki-content maincontent"><h3 id="ScriptingLanguagesContext-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" 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="ScriptingLanguagesContext-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/scripting-languages.html
==============================================================================
--- websites/production/camel/content/scripting-languages.html (original)
+++ websites/production/camel/content/scripting-languages.html Wed Feb 18 07:19:31 2015
@@ -97,7 +97,7 @@
 
 <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="ScriptingLanguages-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="confluence
 Td"><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="ScriptingLanguages-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="ScriptingLanguages-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="confluence
 Td"><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="ScriptingLanguages-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()) {



Mime
View raw message