camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r887566 - in /websites/production/camel/content: book-component-appendix.html book-in-one-page.html cache/main.pageCache camel-2130-release.html language.html
Date Thu, 21 Nov 2013 17:20:59 GMT
Author: buildbot
Date: Thu Nov 21 17:20:59 2013
New Revision: 887566

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/camel-2130-release.html
    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 Thu Nov 21 17:20:59 2013
@@ -10386,7 +10386,7 @@ language://languageName:resource:scheme:
 <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"> Name </th><th colspan="1" rowspan="1" class="confluenceTh">
Default Value </th><th colspan="1" rowspan="1" class="confluenceTh"> Type </th><th
colspan="1" rowspan="1" class="confluenceTh"> Description </th></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>languageName</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>String</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> The name of the <a shape="rect" href="languages.html"
title="Languages">Language</a> to use, such as <tt>simple</tt>, <tt>groovy</tt>,
<tt>javascript</tt> etc. This option is mandatory. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>script</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>String</tt> </td><td
colspan=
 "1" rowspan="1" class="confluenceTd"> The script to execute. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>transform</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>true</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>boolean</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> Whether or not the result of the script should
be used as the new message body. By setting to <tt>false</tt> the script is executed
but the result of the script is discarded. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>contentCache</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>true</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>boolean</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <b>Camel 2.9:</b> Whether to cache the script
if loaded from a resource.<br clear="none">
-Note: from <b>Camel 2.10.3</b> a cached script can be forced to reload at runtime
via JMX using the clearContentCache operation. </td></tr></tbody></table>
+Note: from <b>Camel 2.10.3</b> a cached script can be forced to reload at runtime
via JMX using the clearContentCache operation. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>cacheScript</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>boolean</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <b>Camel 2.13/2.12.2/2.11.3:</b> 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. </td></tr></tbody></table>
 </div>
 </div>
 

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 Thu Nov 21 17:20:59 2013
@@ -31969,7 +31969,7 @@ language://languageName:resource:scheme:
 <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"> Name </th><th colspan="1" rowspan="1" class="confluenceTh">
Default Value </th><th colspan="1" rowspan="1" class="confluenceTh"> Type </th><th
colspan="1" rowspan="1" class="confluenceTh"> Description </th></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>languageName</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>String</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> The name of the <a shape="rect" href="languages.html"
title="Languages">Language</a> to use, such as <tt>simple</tt>, <tt>groovy</tt>,
<tt>javascript</tt> etc. This option is mandatory. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>script</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>String</tt> </td><td
colspan=
 "1" rowspan="1" class="confluenceTd"> The script to execute. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>transform</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>true</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>boolean</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> Whether or not the result of the script should
be used as the new message body. By setting to <tt>false</tt> the script is executed
but the result of the script is discarded. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>contentCache</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>true</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>boolean</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <b>Camel 2.9:</b> Whether to cache the script
if loaded from a resource.<br clear="none">
-Note: from <b>Camel 2.10.3</b> a cached script can be forced to reload at runtime
via JMX using the clearContentCache operation. </td></tr></tbody></table>
+Note: from <b>Camel 2.10.3</b> a cached script can be forced to reload at runtime
via JMX using the clearContentCache operation. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>cacheScript</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>boolean</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <b>Camel 2.13/2.12.2/2.11.3:</b> 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. </td></tr></tbody></table>
 </div>
 </div>
 

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

Modified: websites/production/camel/content/camel-2130-release.html
==============================================================================
--- websites/production/camel/content/camel-2130-release.html (original)
+++ websites/production/camel/content/camel-2130-release.html Thu Nov 21 17:20:59 2013
@@ -151,7 +151,7 @@
 
 
 <h2><a shape="rect" name="Camel2.13.0Release-Changesthatmayaffectendusers"></a>Changes
that may affect end users</h2>
-<ul><li>Components depending on Servlet API has been upgrade from Servlet API
2.5 to 3.0</li><li>Jetty upgraded from 7.6.x to 8.1.x</li><li><a
shape="rect" href="hazelcast-component.html" title="Hazelcast Component">Hazelcast Component</a>
uses <tt>Object</tt> instead of <tt>String</tt> as the key.</li><li><a
shape="rect" href="hazelcast-component.html" title="Hazelcast Component">Hazelcast Component</a>
atomic number producer was using incorrect name (<a shape="rect" class="external-link"
href="https://issues.apache.org/jira/browse/CAMEL-6833">CAMEL-6833</a>).  Name will
be different with this release.</li><li><a shape="rect" href="hazelcast-component.html"
title="Hazelcast Component">Hazelcast Component</a> instance consumer was incorrectly
writing headers to the "out" message as opposed to the "in" message.  Headers are now written
to the "in" message.</li><li><a shape="rect" href="hazelcast-component.html"
title="Hazelcast Component">Hazelcast Component</a> map/multimap consumer
  were sending header value "envict" when an item was evicted.  This has been corrected and
the value "evicted" is used now.</li><li>The enum value <tt>NON_BLOCKING</tt>
has been removed in <tt>camel-apns</tt> as its no longer support in APNS itself.</li><li><tt>DefaultTimeoutMap</tt>
must call <tt>start</tt> to initialize the map before use.</li><li><tt>@ExcludeRoutes</tt>
test annotation now accepts only classes implementing <tt>RoutesBuilder</tt> interface.</li><li>The
MBean names registered by <a shape="rect" href="camel-jmx.html" title="Camel JMX">Camel
JMX</a> no longer include the hostname in the <tt>context</tt> part, eg
before <tt>context=myHost/myCamelId</tt> and now after <tt>context=myCamelId</tt>.
Having the hostname in the MBean name does not bring much value, and in fact makes things
more complicated as the mbean name changes depending on the host running Camel. There is an
option <tt>includeHostName</tt> that can be configure as <tt>true</tt>
to preserve the old behav
 ior.</li><li><a shape="rect" href="camel-jmx.html" title="Camel JMX">MBean
naming</a> in OSGi cleaned up to use simpler naming with symbolicName. Before we could
have MBean names with duplicate bundle ids such as <tt>context=114-114-camel-6</tt>,
which now is using the symbolic name instead, <tt>context=MyApplication</tt>.</li><li>Added
<tt>beforeAddRoutes</tt> and <tt>afterAddRoutes</tt> to <tt>org.apache.camel.component.servletlistener.CamelContextLifecycle</tt>
in <a shape="rect" href="servletlistener-component.html" title="ServletListener Component">ServletListener
Component</a></li></ul>
+<ul><li>Components depending on Servlet API has been upgrade from Servlet API
2.5 to 3.0</li><li>Jetty upgraded from 7.6.x to 8.1.x</li><li><a
shape="rect" href="hazelcast-component.html" title="Hazelcast Component">Hazelcast Component</a>
uses <tt>Object</tt> instead of <tt>String</tt> as the key.</li><li><a
shape="rect" href="hazelcast-component.html" title="Hazelcast Component">Hazelcast Component</a>
atomic number producer was using incorrect name (<a shape="rect" class="external-link"
href="https://issues.apache.org/jira/browse/CAMEL-6833">CAMEL-6833</a>).  Name will
be different with this release.</li><li><a shape="rect" href="hazelcast-component.html"
title="Hazelcast Component">Hazelcast Component</a> instance consumer was incorrectly
writing headers to the "out" message as opposed to the "in" message.  Headers are now written
to the "in" message.</li><li><a shape="rect" href="hazelcast-component.html"
title="Hazelcast Component">Hazelcast Component</a> map/multimap consumer
  were sending header value "envict" when an item was evicted.  This has been corrected and
the value "evicted" is used now.</li><li>The enum value <tt>NON_BLOCKING</tt>
has been removed in <tt>camel-apns</tt> as its no longer support in APNS itself.</li><li><tt>DefaultTimeoutMap</tt>
must call <tt>start</tt> to initialize the map before use.</li><li><tt>@ExcludeRoutes</tt>
test annotation now accepts only classes implementing <tt>RoutesBuilder</tt> interface.</li><li>The
MBean names registered by <a shape="rect" href="camel-jmx.html" title="Camel JMX">Camel
JMX</a> no longer include the hostname in the <tt>context</tt> part, eg
before <tt>context=myHost/myCamelId</tt> and now after <tt>context=myCamelId</tt>.
Having the hostname in the MBean name does not bring much value, and in fact makes things
more complicated as the mbean name changes depending on the host running Camel. There is an
option <tt>includeHostName</tt> that can be configure as <tt>true</tt>
to preserve the old behav
 ior.</li><li><a shape="rect" href="camel-jmx.html" title="Camel JMX">MBean
naming</a> in OSGi cleaned up to use simpler naming with symbolicName. Before we could
have MBean names with duplicate bundle ids such as <tt>context=114-114-camel-6</tt>,
which now is using the symbolic name instead, <tt>context=MyApplication</tt>.</li><li>Added
<tt>beforeAddRoutes</tt> and <tt>afterAddRoutes</tt> to <tt>org.apache.camel.component.servletlistener.CamelContextLifecycle</tt>
in <a shape="rect" href="servletlistener-component.html" title="ServletListener Component">ServletListener
Component</a></li><li>The <a shape="rect" href="language.html" title="Language">Language</a>
component now no longer caches the compiled script as that could cause side-effects. You can
set <tt>cacheScript=true</tt> to enable the previous behavior if your script is
safe to do so.</li></ul>
 
 
 

Modified: websites/production/camel/content/language.html
==============================================================================
--- websites/production/camel/content/language.html (original)
+++ websites/production/camel/content/language.html Thu Nov 21 17:20:59 2013
@@ -112,7 +112,7 @@ language://languageName:resource:scheme:
 <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"> Name </th><th colspan="1" rowspan="1" class="confluenceTh">
Default Value </th><th colspan="1" rowspan="1" class="confluenceTh"> Type </th><th
colspan="1" rowspan="1" class="confluenceTh"> Description </th></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>languageName</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>String</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> The name of the <a shape="rect" href="languages.html"
title="Languages">Language</a> to use, such as <tt>simple</tt>, <tt>groovy</tt>,
<tt>javascript</tt> etc. This option is mandatory. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>script</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>String</tt> </td><td
colspan=
 "1" rowspan="1" class="confluenceTd"> The script to execute. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>transform</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>true</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>boolean</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> Whether or not the result of the script should
be used as the new message body. By setting to <tt>false</tt> the script is executed
but the result of the script is discarded. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>contentCache</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>true</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>boolean</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <b>Camel 2.9:</b> Whether to cache the script
if loaded from a resource.<br clear="none">
-Note: from <b>Camel 2.10.3</b> a cached script can be forced to reload at runtime
via JMX using the clearContentCache operation. </td></tr></tbody></table>
+Note: from <b>Camel 2.10.3</b> a cached script can be forced to reload at runtime
via JMX using the clearContentCache operation. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>cacheScript</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>boolean</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <b>Camel 2.13/2.12.2/2.11.3:</b> 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. </td></tr></tbody></table>
 </div>
 </div>
 



Mime
View raw message