Author: buildbot
Date: Tue Jun 11 19:22:17 2013
New Revision: 865328
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/book-in-one-page.html
websites/production/camel/content/book-pattern-appendix.html
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/exception-clause.html
websites/production/camel/content/splitter.html
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 Tue Jun 11 19:22:17
2013
@@ -16788,7 +16788,7 @@ from(<span class="code-quote">"direct:c"
<h3><a shape="rect" name="BookInOnePage-Options"></a>Options</h3>
<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"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>strategyRef</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Refers to an <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/processor/aggregate/AggregationStrategy.html";>AggregationStrategy</a>
to be used to assemble the replies from the sub-messages, into a single
outgoing message from the <a shape="rect" href="splitter.html"
title="Splitter">Splitter</a>. See the defaults described below in <em><a
shape="rect" href="#BookInOnePage-WhattheSplitterreturns">What the Splitter
returns</a></em>. </td></tr><tr><td colspan="1" rowspan="1" class="con
fluenceTd"> <tt>parallelProcessing</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> If enables then processing the sub-messages occurs
concurrently. Note the caller thread will still wait until all sub-messages has
been fully processed, before it continues. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>executorServiceRef</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1"
rowspan="1" class="confluenceTd"> Refers to a custom <a shape="rect"
href="threading-model.html" title="Threading Model">Thread Pool</a> to be used
for parallel processing. Notice if you set this option, then parallel
processing is automatic implied, and you do not have to enable that option as
well. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>stopOnException</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>false</tt> </td><td colspan
="1" rowspan="1" class="confluenceTd"> <b>Camel 2.2:</b> Whether or not to
stop continue processing immediately when an exception occurred. If disable,
then Camel continue splitting and process the sub-messages regardless if one of
them failed. You can deal with exceptions in the <a shape="rect"
class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/processor/aggregate/AggregationStrategy.html";>AggregationStrategy</a>
class where you have full control how to handle that. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>streaming</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> If enabled then Camel will split
in a streaming fashion, which means it will split the input message in chunks.
This reduces the memory overhead. For example if you split big messages its
recommended to enable streaming. If streaming is enabled then the sub-
message replies will be aggregated out-of-order, eg in the order they come
back. If disabled, Camel will process sub-message replies in the same order as
they where splitted. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>timeout</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.5:</b> Sets a total timeout specified in
millis. If the <a shape="rect" href="recipient-list.html" title="Recipient
List">Recipient List</a> hasn't been able to split and process all replies
within the given timeframe, then the timeout triggers and the <a shape="rect"
href="splitter.html" title="Splitter">Splitter</a> breaks out and continues.
Notice if you provide a <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/processor/aggregate/TimeoutAwareAggregationStrategy.html";>TimeoutAwareAggregationStrategy</a>
then the <tt>timeout</tt>
method is invoked before breaking out. If the timeout is reached with running
tasks still remaining, certain tasks for which it is difficult for Camel to
shut down in a graceful manner may continue to run. So use this option with a
bit of care. We may be able to improve this functionality in future Camel
releases. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>onPrepareRef</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.8:</b> Refers to a custom <a shape="rect"
href="processor.html" title="Processor">Processor</a> to prepare the
sub-message of the <a shape="rect" href="exchange.html"
title="Exchange">Exchange</a>, before its processed. This allows you to do any
custom logic, such as deep-cloning the message payload if that's needed etc.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>shareUnitOfWork</tt> </td><td colspan="1" rowspan="1" class="conflu
enceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<b>Camel 2.8:</b> Whether the unit of work should be shared. See further below
for more details. </td></tr></tbody></table>
+<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"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>strategyRef</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Refers to an <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/processor/aggregate/AggregationStrategy.html";>AggregationStrategy</a>
to be used to assemble the replies from the sub-messages, into a single
outgoing message from the <a shape="rect" href="splitter.html"
title="Splitter">Splitter</a>. See the defaults described below in <em><a
shape="rect" href="#BookInOnePage-WhattheSplitterreturns">What the Splitter
returns</a></em>. </td></tr><tr><td colspan="1" rowspan="1" class="con
fluenceTd"> <tt>parallelProcessing</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> If enabled then processing the sub-messages occurs
concurrently. Note the caller thread will still wait until all sub-messages has
been fully processed, before it continues. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>executorServiceRef</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1"
rowspan="1" class="confluenceTd"> Refers to a custom <a shape="rect"
href="threading-model.html" title="Threading Model">Thread Pool</a> to be used
for parallel processing. Notice if you set this option, then parallel
processing is automatically implied, and you do not have to enable that option
as well. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>stopOnException</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>false</tt> </td><td col
span="1" rowspan="1" class="confluenceTd"> <b>Camel 2.2:</b> Whether or not to
stop continue processing immediately when an exception occurred. If disable,
then Camel continue splitting and process the sub-messages regardless if one of
them failed. You can deal with exceptions in the <a shape="rect"
class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/processor/aggregate/AggregationStrategy.html";>AggregationStrategy</a>
class where you have full control how to handle that. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>streaming</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> If enabled then Camel will split
in a streaming fashion, which means it will split the input message in chunks.
This reduces the memory overhead. For example if you split big messages its
recommended to enable streaming. If streaming is enabled then the
sub-message replies will be aggregated out-of-order, eg in the order they come
back. If disabled, Camel will process sub-message replies in the same order as
they where splitted. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>timeout</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.5:</b> Sets a total timeout specified in
millis. If the <a shape="rect" href="recipient-list.html" title="Recipient
List">Recipient List</a> hasn't been able to split and process all replies
within the given timeframe, then the timeout triggers and the <a shape="rect"
href="splitter.html" title="Splitter">Splitter</a> breaks out and continues.
Notice if you provide a <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/processor/aggregate/TimeoutAwareAggregationStrategy.html";>TimeoutAwareAggregationStrategy</a>
then the <tt>timeout<
/tt> method is invoked before breaking out. If the timeout is reached with
running tasks still remaining, certain tasks for which it is difficult for
Camel to shut down in a graceful manner may continue to run. So use this
option with a bit of care. We may be able to improve this functionality in
future Camel releases. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>onPrepareRef</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.8:</b> Refers to a custom <a shape="rect"
href="processor.html" title="Processor">Processor</a> to prepare the
sub-message of the <a shape="rect" href="exchange.html"
title="Exchange">Exchange</a>, before its processed. This allows you to do any
custom logic, such as deep-cloning the message payload if that's needed etc.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>shareUnitOfWork</tt> </td><td colspan="1" rowspan="1" class="co
nfluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.8:</b> Whether the unit of work should be
shared. See further below for more details. </td></tr></tbody></table>
</div>
</div>
Modified: websites/production/camel/content/book-pattern-appendix.html
==============================================================================
--- websites/production/camel/content/book-pattern-appendix.html (original)
+++ websites/production/camel/content/book-pattern-appendix.html Tue Jun 11
19:22:17 2013
@@ -1720,7 +1720,7 @@ from(<span class="code-quote">"direct:c"
<h3><a shape="rect" name="BookPatternAppendix-Options"></a>Options</h3>
<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"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>strategyRef</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Refers to an <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/processor/aggregate/AggregationStrategy.html";>AggregationStrategy</a>
to be used to assemble the replies from the sub-messages, into a single
outgoing message from the <a shape="rect" href="splitter.html"
title="Splitter">Splitter</a>. See the defaults described below in <em><a
shape="rect" href="#BookPatternAppendix-WhattheSplitterreturns">What the
Splitter returns</a></em>. </td></tr><tr><td colspan="1" rowspan="1" clas
s="confluenceTd"> <tt>parallelProcessing</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> If enables then processing the sub-messages occurs
concurrently. Note the caller thread will still wait until all sub-messages has
been fully processed, before it continues. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>executorServiceRef</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1"
rowspan="1" class="confluenceTd"> Refers to a custom <a shape="rect"
href="threading-model.html" title="Threading Model">Thread Pool</a> to be used
for parallel processing. Notice if you set this option, then parallel
processing is automatic implied, and you do not have to enable that option as
well. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>stopOnException</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>false</tt> </td><td c
olspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.2:</b> Whether or not
to stop continue processing immediately when an exception occurred. If disable,
then Camel continue splitting and process the sub-messages regardless if one of
them failed. You can deal with exceptions in the <a shape="rect"
class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/processor/aggregate/AggregationStrategy.html";>AggregationStrategy</a>
class where you have full control how to handle that. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>streaming</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> If enabled then Camel will split
in a streaming fashion, which means it will split the input message in chunks.
This reduces the memory overhead. For example if you split big messages its
recommended to enable streaming. If streaming is enabled then th
e sub-message replies will be aggregated out-of-order, eg in the order they
come back. If disabled, Camel will process sub-message replies in the same
order as they where splitted. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>timeout</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.5:</b> Sets a total timeout specified in
millis. If the <a shape="rect" href="recipient-list.html" title="Recipient
List">Recipient List</a> hasn't been able to split and process all replies
within the given timeframe, then the timeout triggers and the <a shape="rect"
href="splitter.html" title="Splitter">Splitter</a> breaks out and continues.
Notice if you provide a <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/processor/aggregate/TimeoutAwareAggregationStrategy.html";>TimeoutAwareAggregationStrategy</a>
then the <tt>timeou
t</tt> method is invoked before breaking out. If the timeout is reached with
running tasks still remaining, certain tasks for which it is difficult for
Camel to shut down in a graceful manner may continue to run. So use this
option with a bit of care. We may be able to improve this functionality in
future Camel releases. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>onPrepareRef</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.8:</b> Refers to a custom <a shape="rect"
href="processor.html" title="Processor">Processor</a> to prepare the
sub-message of the <a shape="rect" href="exchange.html"
title="Exchange">Exchange</a>, before its processed. This allows you to do any
custom logic, such as deep-cloning the message payload if that's needed etc.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>shareUnitOfWork</tt> </td><td colspan="1" rowspan="1" class="
confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.8:</b> Whether the unit of work should be
shared. See further below for more details. </td></tr></tbody></table>
+<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"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>strategyRef</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Refers to an <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/processor/aggregate/AggregationStrategy.html";>AggregationStrategy</a>
to be used to assemble the replies from the sub-messages, into a single
outgoing message from the <a shape="rect" href="splitter.html"
title="Splitter">Splitter</a>. See the defaults described below in <em><a
shape="rect" href="#BookPatternAppendix-WhattheSplitterreturns">What the
Splitter returns</a></em>. </td></tr><tr><td colspan="1" rowspan="1" clas
s="confluenceTd"> <tt>parallelProcessing</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> If enabled then processing the sub-messages occurs
concurrently. Note the caller thread will still wait until all sub-messages has
been fully processed, before it continues. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>executorServiceRef</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1"
rowspan="1" class="confluenceTd"> Refers to a custom <a shape="rect"
href="threading-model.html" title="Threading Model">Thread Pool</a> to be used
for parallel processing. Notice if you set this option, then parallel
processing is automatically implied, and you do not have to enable that option
as well. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>stopOnException</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>false</tt> </td><
td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.2:</b> Whether or
not to stop continue processing immediately when an exception occurred. If
disable, then Camel continue splitting and process the sub-messages regardless
if one of them failed. You can deal with exceptions in the <a shape="rect"
class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/processor/aggregate/AggregationStrategy.html";>AggregationStrategy</a>
class where you have full control how to handle that. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>streaming</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> If enabled then Camel will split
in a streaming fashion, which means it will split the input message in chunks.
This reduces the memory overhead. For example if you split big messages its
recommended to enable streaming. If streaming is enabled the
n the sub-message replies will be aggregated out-of-order, eg in the order
they come back. If disabled, Camel will process sub-message replies in the same
order as they where splitted. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>timeout</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.5:</b> Sets a total timeout specified in
millis. If the <a shape="rect" href="recipient-list.html" title="Recipient
List">Recipient List</a> hasn't been able to split and process all replies
within the given timeframe, then the timeout triggers and the <a shape="rect"
href="splitter.html" title="Splitter">Splitter</a> breaks out and continues.
Notice if you provide a <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/processor/aggregate/TimeoutAwareAggregationStrategy.html";>TimeoutAwareAggregationStrategy</a>
then the <tt>ti
meout</tt> method is invoked before breaking out. If the timeout is reached
with running tasks still remaining, certain tasks for which it is difficult for
Camel to shut down in a graceful manner may continue to run. So use this
option with a bit of care. We may be able to improve this functionality in
future Camel releases. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>onPrepareRef</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.8:</b> Refers to a custom <a shape="rect"
href="processor.html" title="Processor">Processor</a> to prepare the
sub-message of the <a shape="rect" href="exchange.html"
title="Exchange">Exchange</a>, before its processed. This allows you to do any
custom logic, such as deep-cloning the message payload if that's needed etc.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>shareUnitOfWork</tt> </td><td colspan="1" rowspan="1" cla
ss="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.8:</b> Whether the unit of work should be
shared. See further below for more details. </td></tr></tbody></table>
</div>
</div>
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/exception-clause.html
==============================================================================
--- websites/production/camel/content/exception-clause.html (original)
+++ websites/production/camel/content/exception-clause.html Tue Jun 11 19:22:17
2013
@@ -237,13 +237,11 @@ You can reference a <tt>RedeliveryPolicy
<span class="code-tag"><property name=<span
class="code-quote">"maximumRedeliveries"</span> value=<span
class="code-quote">"${myprop.max}"</span>/></span>
<span class="code-tag"></bean></span>
- <span class="code-tag"><onException></span>
+ <span class="code-tag"><span class="code-comment"><!-- here we
reference our redelivery policy defined above --></span></span>
+ <span class="code-tag"><onException redeliveryPolicyRef=<span
class="code-quote">"myRedeliveryPolicy"</span>></span>
<span class="code-tag"><span class="code-comment"><!-- you can
define multiple exceptions just adding more exception elements as show below
--></span></span>
<span
class="code-tag"><exception></span>com.mycompany.MyFirstException<span
class="code-tag"></exception></span>
<span
class="code-tag"><exception></span>com.mycompany.MySecondException<span
class="code-tag"></exception></span>
-
- <span class="code-tag"><span class="code-comment"><!-- here we
reference our redelivery policy defined above --></span></span>
- <span class="code-tag"><redeliveryPolicy ref=<span
class="code-quote">"myRedeliveryPolicy"</span>/></span>
<span class="code-tag"></onException></span>
</pre>
</div></div>
Modified: websites/production/camel/content/splitter.html
==============================================================================
--- websites/production/camel/content/splitter.html (original)
+++ websites/production/camel/content/splitter.html Tue Jun 11 19:22:17 2013
@@ -87,7 +87,7 @@
<h3><a shape="rect" name="Splitter-Options"></a>Options</h3>
<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"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>strategyRef</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Refers to an <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/processor/aggregate/AggregationStrategy.html";>AggregationStrategy</a>
to be used to assemble the replies from the sub-messages, into a single
outgoing message from the <a shape="rect" href="splitter.html"
title="Splitter">Splitter</a>. See the defaults described below in <em><a
shape="rect" href="#Splitter-WhattheSplitterreturns">What the Splitter
returns</a></em>. </td></tr><tr><td colspan="1" rowspan="1" class="confluen
ceTd"> <tt>parallelProcessing</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> If enables then processing the sub-messages occurs
concurrently. Note the caller thread will still wait until all sub-messages has
been fully processed, before it continues. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>executorServiceRef</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1"
rowspan="1" class="confluenceTd"> Refers to a custom <a shape="rect"
href="threading-model.html" title="Threading Model">Thread Pool</a> to be used
for parallel processing. Notice if you set this option, then parallel
processing is automatic implied, and you do not have to enable that option as
well. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>stopOnException</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>false</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <b>Camel 2.2:</b> Whether or not to stop
continue processing immediately when an exception occurred. If disable, then
Camel continue splitting and process the sub-messages regardless if one of them
failed. You can deal with exceptions in the <a shape="rect"
class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/processor/aggregate/AggregationStrategy.html";>AggregationStrategy</a>
class where you have full control how to handle that. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>streaming</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> If enabled then Camel will split
in a streaming fashion, which means it will split the input message in chunks.
This reduces the memory overhead. For example if you split big messages its
recommended to enable streaming. If streaming is enabled then the sub-messa
ge replies will be aggregated out-of-order, eg in the order they come back. If
disabled, Camel will process sub-message replies in the same order as they
where splitted. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>timeout</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.5:</b> Sets a total timeout specified in
millis. If the <a shape="rect" href="recipient-list.html" title="Recipient
List">Recipient List</a> hasn't been able to split and process all replies
within the given timeframe, then the timeout triggers and the <a shape="rect"
href="splitter.html" title="Splitter">Splitter</a> breaks out and continues.
Notice if you provide a <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/processor/aggregate/TimeoutAwareAggregationStrategy.html";>TimeoutAwareAggregationStrategy</a>
then the <tt>timeout</tt> meth
od is invoked before breaking out. If the timeout is reached with running
tasks still remaining, certain tasks for which it is difficult for Camel to
shut down in a graceful manner may continue to run. So use this option with a
bit of care. We may be able to improve this functionality in future Camel
releases. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>onPrepareRef</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.8:</b> Refers to a custom <a shape="rect"
href="processor.html" title="Processor">Processor</a> to prepare the
sub-message of the <a shape="rect" href="exchange.html"
title="Exchange">Exchange</a>, before its processed. This allows you to do any
custom logic, such as deep-cloning the message payload if that's needed etc.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>shareUnitOfWork</tt> </td><td colspan="1" rowspan="1" class="confluenceT
d"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<b>Camel 2.8:</b> Whether the unit of work should be shared. See further below
for more details. </td></tr></tbody></table>
+<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"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>strategyRef</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Refers to an <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/processor/aggregate/AggregationStrategy.html";>AggregationStrategy</a>
to be used to assemble the replies from the sub-messages, into a single
outgoing message from the <a shape="rect" href="splitter.html"
title="Splitter">Splitter</a>. See the defaults described below in <em><a
shape="rect" href="#Splitter-WhattheSplitterreturns">What the Splitter
returns</a></em>. </td></tr><tr><td colspan="1" rowspan="1" class="confluen
ceTd"> <tt>parallelProcessing</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> If enabled then processing the sub-messages occurs
concurrently. Note the caller thread will still wait until all sub-messages has
been fully processed, before it continues. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>executorServiceRef</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1"
rowspan="1" class="confluenceTd"> Refers to a custom <a shape="rect"
href="threading-model.html" title="Threading Model">Thread Pool</a> to be used
for parallel processing. Notice if you set this option, then parallel
processing is automatically implied, and you do not have to enable that option
as well. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>stopOnException</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>false</tt> </td><td colspan=
"1" rowspan="1" class="confluenceTd"> <b>Camel 2.2:</b> Whether or not to stop
continue processing immediately when an exception occurred. If disable, then
Camel continue splitting and process the sub-messages regardless if one of them
failed. You can deal with exceptions in the <a shape="rect"
class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/processor/aggregate/AggregationStrategy.html";>AggregationStrategy</a>
class where you have full control how to handle that. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>streaming</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> If enabled then Camel will split
in a streaming fashion, which means it will split the input message in chunks.
This reduces the memory overhead. For example if you split big messages its
recommended to enable streaming. If streaming is enabled then the sub-m
essage replies will be aggregated out-of-order, eg in the order they come
back. If disabled, Camel will process sub-message replies in the same order as
they where splitted. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>timeout</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.5:</b> Sets a total timeout specified in
millis. If the <a shape="rect" href="recipient-list.html" title="Recipient
List">Recipient List</a> hasn't been able to split and process all replies
within the given timeframe, then the timeout triggers and the <a shape="rect"
href="splitter.html" title="Splitter">Splitter</a> breaks out and continues.
Notice if you provide a <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/processor/aggregate/TimeoutAwareAggregationStrategy.html";>TimeoutAwareAggregationStrategy</a>
then the <tt>timeout</tt>
method is invoked before breaking out. If the timeout is reached with running
tasks still remaining, certain tasks for which it is difficult for Camel to
shut down in a graceful manner may continue to run. So use this option with a
bit of care. We may be able to improve this functionality in future Camel
releases. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>onPrepareRef</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.8:</b> Refers to a custom <a shape="rect"
href="processor.html" title="Processor">Processor</a> to prepare the
sub-message of the <a shape="rect" href="exchange.html"
title="Exchange">Exchange</a>, before its processed. This allows you to do any
custom logic, such as deep-cloning the message payload if that's needed etc.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>shareUnitOfWork</tt> </td><td colspan="1" rowspan="1" class="conflue
nceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<b>Camel 2.8:</b> Whether the unit of work should be shared. See further below
for more details. </td></tr></tbody></table>
</div>
</div>
