camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r875463 [2/3] - in /websites/production/camel/content: aggregator2.html book-in-one-page.html book-pattern-appendix.html cache/main.pageCache content-enricher.html multicast.html recipient-list.html splitter.html
Date Tue, 20 Aug 2013 12:21:46 GMT
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 Aug 20 12:21:45 2013
@@ -1406,7 +1406,7 @@ public class MyDynamicRouter {
 <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>delimiter</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>,</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Delimiter used if the <a shape="rect" href="expression.html" title="Expression">Expression</a> returned multiple endpoints. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>strategyRef</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> 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> that will assemble the replies from recipient
 s into a single outgoing message from the <a shape="rect" href="recipient-list.html" title="Recipient List">Recipient List</a>. By default Camel will use the last reply as the outgoing message. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>parallelProcessing</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> If enabled, messages are sent to the recipients concurrently. Note that the calling thread will still wait until all messages have been fully processed before it continues; it's the sending and processing of replies from recipients which happens in parallel. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>executorServiceRef</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.2:</b> A custom <a shape="rect" href="threading-model.html" title="Threading Model">Thread 
 Pool</a> to use for parallel processing. Note that enabling this option implies parallel processing, so you need not 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 to immediately stop processing when an exception occurs. If disabled, Camel will send the message to all recipients regardless of any individual failures. You can process exceptions in 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> implementation, which supports full control of error handling. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>ignoreInvalidEndpoints</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><t
 d colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.3:</b> Whether to ignore an endpoint URI that could not be resolved. If disabled, Camel will throw an exception identifying the invalid endpoint URI. </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"> <b>Camel 2.5:</b> If enabled, Camel will process replies out-of-order - that is, in the order received in reply from each recipient. If disabled, Camel will process replies in the same order as specified by the <a shape="rect" href="expression.html" title="Expression">Expression</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>timeout</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.5:</b> Specifies a processing timeout milliseconds. If the <a shape="rect" href="recipie
 nt-list.html" title="Recipient List">Recipient List</a> hasn't been able to send and process all replies within this timeframe, then the timeout triggers and the <a shape="rect" href="recipient-list.html" title="Recipient List">Recipient List</a> breaks out, with message flow continuing to the next element. Note that 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>, its <tt>timeout</tt> method is invoked before breaking out. <b>Beware:</b> 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">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.8:</b> A custom <a shape="rect" href="processor.html" title="Processor">Processor</a> to prepare the copy of the <a shape="rect" href="exchange.html" title="Exchange">Exchange</a> each recipient will receive. This allows you to perform arbitrary transformations, such as deep-cloning the message payload (or any other custom logic). </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 <a shape="rect" href="splitter.html#Splitter-Sharingunitofwork">the same option on Splitter</a> 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>delimiter</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>,</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Delimiter used if the <a shape="rect" href="expression.html" title="Expression">Expression</a> returned multiple endpoints. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>strategyRef</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> 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> that will assemble the replies from recipient
 s into a single outgoing message from the <a shape="rect" href="recipient-list.html" title="Recipient List">Recipient List</a>. By default Camel will use the last reply as the outgoing message. From <b>Camel 2.12</b> onwards you can also use a POJO as the <tt>AggregationStrategy</tt>, see the <a shape="rect" href="aggregator2.html" title="Aggregator2">Aggregate</a> page for more details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>strategyMethodName</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.12:</b> This option can be used to explicit declare the method name to use, when using POJOs as the <tt>AggregationStrategy</tt>. See the <a shape="rect" href="aggregator2.html" title="Aggregator2">Aggregate</a> page for more details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>strategyMethodAllowNull</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <
 tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.12:</b> If this option is <tt>false</tt> then the aggregate method is not used if there was no data to enrich. If this option is <tt>true</tt> then <tt>null</tt> values is used as the <tt>oldExchange</tt> (when no data to enrich), when using POJOs as the <tt>AggregationStrategy</tt>. See the <a shape="rect" href="aggregator2.html" title="Aggregator2">Aggregate</a> page for more details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>parallelProcessing</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> If enabled, messages are sent to the recipients concurrently. Note that the calling thread will still wait until all messages have been fully processed before it continues; it's the sending and processing of replies from recipients which happens in parallel. </td></tr><tr><td colspan="1" row
 span="1" class="confluenceTd"> <tt>executorServiceRef</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.2:</b> A custom <a shape="rect" href="threading-model.html" title="Threading Model">Thread Pool</a> to use for parallel processing. Note that enabling this option implies parallel processing, so you need not 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 to immediately stop processing when an exception occurs. If disabled, Camel will send the message to all recipients regardless of any individual failures. You can process exceptions in an <a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/processor/aggregate/Aggregatio
 nStrategy.html">AggregationStrategy</a> implementation, which supports full control of error handling. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>ignoreInvalidEndpoints</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.3:</b> Whether to ignore an endpoint URI that could not be resolved. If disabled, Camel will throw an exception identifying the invalid endpoint URI. </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"> <b>Camel 2.5:</b> If enabled, Camel will process replies out-of-order - that is, in the order received in reply from each recipient. If disabled, Camel will process replies in the same order as specified by the <a shape="rect" href="expression.html" title="Expression">Expression</a>. </td></tr><tr><td c
 olspan="1" rowspan="1" class="confluenceTd"> <tt>timeout</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.5:</b> Specifies a processing timeout milliseconds. If the <a shape="rect" href="recipient-list.html" title="Recipient List">Recipient List</a> hasn't been able to send and process all replies within this timeframe, then the timeout triggers and the <a shape="rect" href="recipient-list.html" title="Recipient List">Recipient List</a> breaks out, with message flow continuing to the next element. Note that 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>, its <tt>timeout</tt> method is invoked before breaking out. <b>Beware:</b> If the timeout is reached with running tasks still remaining, certain tasks for which it is diffi
 cult 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">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.8:</b> A custom <a shape="rect" href="processor.html" title="Processor">Processor</a> to prepare the copy of the <a shape="rect" href="exchange.html" title="Exchange">Exchange</a> each recipient will receive. This allows you to perform arbitrary transformations, such as deep-cloning the message payload (or any other custom logic). </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 sha
 red. See <a shape="rect" href="splitter.html#Splitter-Sharingunitofwork">the same option on Splitter</a> for more details. </td></tr></tbody></table>
 </div>
 </div>
 
@@ -1781,7 +1781,7 @@ public interface TimeoutAwareAggregation
 <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">&#160;</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>. From <b>Camel 2.12</b> onwards you can also use a POJO
  as the <tt>AggregationStrategy</tt>, see the <a shape="rect" href="aggregator2.html" title="Aggregator2">Aggregate</a> page for more details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>strategyMethodName</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.12:</b> This option can be used to explicit declare the method name to use, when using POJOs as the <tt>AggregationStrategy</tt>. See the <a shape="rect" href="aggregator2.html" title="Aggregator2">Aggregate</a> page for more details. </td></tr><tr><td colspan="1" rowspan="1" class="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">&#160;</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/mave
 n/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">&#160;</td><td colspan="1" rowspan="1" class="confl
 uenceTd"> <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="c
 onfluenceTd"> <tt>onPrepareRef</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</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">&#160;</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>. From <b>Camel 2.12</b> onwards you can also use a POJO
  as the <tt>AggregationStrategy</tt>, see the <a shape="rect" href="aggregator2.html" title="Aggregator2">Aggregate</a> page for more details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>strategyMethodName</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.12:</b> This option can be used to explicit declare the method name to use, when using POJOs as the <tt>AggregationStrategy</tt>. See the <a shape="rect" href="aggregator2.html" title="Aggregator2">Aggregate</a> page for more details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>strategyMethodAllowNull</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.12:</b> If this option is <tt>false</tt> then the aggregate method is not used for the very first splitted message. If this option is <tt>true</tt> then <tt>null</tt> v
 alues is used as the <tt>oldExchange</tt> (for the very first message splitted), when using POJOs as the <tt>AggregationStrategy</tt>. See the <a shape="rect" href="aggregator2.html" title="Aggregator2">Aggregate</a> page for more details. </td></tr><tr><td colspan="1" rowspan="1" class="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">&#160;</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 th
 is 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-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">&#160;</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">&#160;</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>
 </div>
 </div>
 
@@ -2822,9 +2822,7 @@ public class MyBodyAppender {
 
 <h4><a shape="rect" name="BookPatternAppendix-Aggregatingwhennodata"></a>Aggregating when no data</h4>
 
-<p>By default when using POJOs as AggregationStrategy, then the method is <b>only</b> invoked when there is data to be aggregated. Where as without using POJOs then you may have <tt>null</tt> as <tt>oldExchange</tt> or <tt>newExchange</tt> parameters. </p>
-
-<p>For example the <a shape="rect" href="aggregator2.html" title="Aggregator2">Aggregate</a> EIP will invoke the <tt>AggregationStrategy</tt> with <tt>oldExchange</tt> as null, for the first <a shape="rect" href="exchange.html" title="Exchange">Exchange</a> incoming to the aggregator. And then for subsequent <a shape="rect" href="exchange.html" title="Exchange">Exchange</a>s then <tt>oldExchange</tt> and <tt>newExchange</tt> parameters are both not null. </p>
+<p>By default when using POJOs as AggregationStrategy, then the method is <b>only</b> invoked when there is data to be aggregated (by default). You can use the option <tt>strategyMethodAllowNull</tt> to configure this. Where as without using POJOs then you may have <tt>null</tt> as <tt>oldExchange</tt> or <tt>newExchange</tt> parameters. For example the <a shape="rect" href="aggregator2.html" title="Aggregator2">Aggregate</a> EIP will invoke the <tt>AggregationStrategy</tt> with <tt>oldExchange</tt> as null, for the first <a shape="rect" href="exchange.html" title="Exchange">Exchange</a> incoming to the aggregator. And then for subsequent <a shape="rect" href="exchange.html" title="Exchange">Exchange</a>s then <tt>oldExchange</tt> and <tt>newExchange</tt> parameters are both not null. </p>
 
 <h5><a shape="rect" name="BookPatternAppendix-ExamplewithContentEnricherandnodata"></a>Example with <a shape="rect" href="content-enricher.html" title="Content Enricher">Content Enricher</a> and no data</h5>
 <p>Though with POJOs as AggregationStrategy we made this simpler and only call the method when <tt>oldExchange</tt> and <tt>newExchange</tt> is not null, as that would be the most common use-case. If you need to allow <tt>oldExchange</tt> or <tt>newExchange</tt> to be null, then you can configure this with the POJO using the <tt>AggregationStrategyBeanAdapter</tt> as shown below. On the bean adapter we call <tt>setAllowNullNewExchange</tt> to allow the new exchange to be null.</p>
@@ -2833,6 +2831,7 @@ public class MyBodyAppender {
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
     public void configure() throws Exception {
         AggregationStrategyBeanAdapter myStrategy = new AggregationStrategyBeanAdapter(appender, "append");
+        myStrategy.setAllowNullOldExchange(true);
         myStrategy.setAllowNullNewExchange(true);
 
         from("direct:start")
@@ -2842,6 +2841,18 @@ public class MyBodyAppender {
 ]]></script>
 </div></div>
 
+<p>This can be configured a bit easier using the <tt>beanAllowNull</tt> method from <tt>AggregationStrategies</tt> as shown:</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
+    public void configure() throws Exception {
+        from("direct:start")
+            .pollEnrich("seda:foo", 1000, AggregationStrategies.beanAllowNull(appender, "append"))
+                .to("mock:result");
+    }
+]]></script>
+</div></div>
+
+
 <p>Then the <tt>append</tt> method in the POJO would need to deal with the situation that <tt>newExchange</tt> can be null:</p>
 <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
@@ -2861,7 +2872,42 @@ public class MyBodyAppender {
 
 <p>In the example above we use the <a shape="rect" href="content-enricher.html" title="Content Enricher">Content Enricher</a> EIP using <tt>pollEnrich</tt>. The <tt>newExchange</tt> will be null in the situation we could not get any data from the "seda:foo" endpoint, and therefore the timeout was hit after 1 second. So if we need to do some special merge logic we would need to set <tt>setAllowNullNewExchange=true</tt>, so the <tt>append</tt> method will be invoked. If we do not do that then when the timeout was hit, then the append method would normally not be invoked, meaning the <a shape="rect" href="content-enricher.html" title="Content Enricher">Content Enricher</a> did not merge/change the message. </p>
 
-<p>There is also a method <tt>setAllowNullOldExchange</tt> to set whether the <tt>oldExchange</tt> is allowed to be null.</p>
+<p>In XML DSL you would configure the <tt>strategyMethodAllowNull</tt> option and set it to true as shown below:</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
+    &lt;camelContext xmlns="http://camel.apache.org/schema/spring"&gt;
+        &lt;route&gt;
+            &lt;from uri="direct:start"/&gt;
+            &lt;aggregate strategyRef="myAppender" strategyMethodName="append" strategyMethodAllowNull="true" completionSize="3"&gt;
+                &lt;correlationExpression&gt;
+                    &lt;constant&gt;true&lt;/constant&gt;
+                &lt;/correlationExpression&gt;
+                &lt;to uri="mock:result"/&gt;
+            &lt;/aggregate&gt;
+        &lt;/route&gt;
+    &lt;/camelContext&gt;
+]]></script>
+</div></div>
+
+<h5><a shape="rect" name="BookPatternAppendix-Differentbodytypes"></a>Different body types</h5>
+
+<p>When for example using <tt>strategyMethodAllowNull</tt> as true, then the parameter types of the message bodies does not have to be the same. For example suppose we want to aggregate from a <tt>com.foo.User</tt> type to a <tt>List&lt;String&gt;</tt> that contains the user name. We could code a POJO doing this as follows:</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
+    public static final class MyUserAppender {
+
+        public List addUsers(List names, User user) {
+            if (names == null) {
+                names = new ArrayList();
+            }
+            names.add(user.getName());
+            return names;
+        }
+    }
+]]></script>
+</div></div>
+
+<p>Notice that the return type is a List which we want to contain the user names. The 1st parameter is the list of names, and then notice the 2nd parameter is the incoming <tt>com.foo.User</tt> type.</p>
 
 <h3><a shape="rect" name="BookPatternAppendix-Seealso"></a>See also</h3>
 <ul class="alternate" type="square"><li>The <a shape="rect" href="loan-broker-example.html" title="Loan Broker Example">Loan Broker Example</a> which uses an aggregator</li><li><a shape="rect" class="external-link" href="http://tmielke.blogspot.com/2009/01/using-camel-aggregator-correctly.html" rel="nofollow">Blog post by Torsten Mielke</a> about using the aggregator correctly.</li><li>The old <a shape="rect" href="aggregator.html" title="Aggregator">Aggregator</a></li><li><a shape="rect" href="hawtdb.html" title="HawtDB">HawtDB</a>, <a shape="rect" href="leveldb.html" title="LevelDB">LevelDB</a> or <a shape="rect" href="sql-component.html" title="SQL Component">SQL Component</a> for persistence support</li><li><a shape="rect" href="aggregate-example.html" title="Aggregate Example">Aggregate Example</a> for an example application</li></ul>
@@ -4235,7 +4281,7 @@ public static class MyLoadBalancer exten
 <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">&#160;</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 multicasts, into a single outgoing message from the <a shape="rect" href="multicast.html" title="Multicast">Multicast</a>. By default Camel will use the last reply as the outgoing message.  From <b>Camel 2.12</b> onwards you can also use a POJO as the <tt>AggregationStrategy</tt>, see the <a shape="rect" href="aggrega
 tor2.html" title="Aggregator2">Aggregate</a> page for more details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>strategyMethodName</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.12:</b> This option can be used to explicit declare the method name to use, when using POJOs as the <tt>AggregationStrategy</tt>. See the <a shape="rect" href="aggregator2.html" title="Aggregator2">Aggregate</a> page for more details. </td></tr><tr><td colspan="1" rowspan="1" class="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 sending messages to the multicasts occurs concurrently. Note the caller thread will still wait until all messages has been fully processed, before it continues. Its only the sending and processing the replies from the multicasts which happens 
 concurrently. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>executorServiceRef</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</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 will send the message to all multicasts regardless if one of them failed. You can deal with exceptions in the <a shape="rect" class="external-link" href="http://camel.apa
 che.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 process replies out-of-order, eg in the order they come back. If disabled, Camel will process replies in the same order as multicasted. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>timeout</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</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="multicast.html" title="Multicast">Multicast</a> hasn't been able to send and process all replies within the given timeframe, then the timeout triggers and the 
 <a shape="rect" href="multicast.html" title="Multicast">Multicast</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">&#160;</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 th
 e copy of the <a shape="rect" href="exchange.html" title="Exchange">Exchange</a> each multicast will receive. 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 the same option on <a shape="rect" href="splitter.html" title="Splitter">Splitter</a> 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">&#160;</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 multicasts, into a single outgoing message from the <a shape="rect" href="multicast.html" title="Multicast">Multicast</a>. By default Camel will use the last reply as the outgoing message.  From <b>Camel 2.12</b> onwards you can also use a POJO as the <tt>AggregationStrategy</tt>, see the <a shape="rect" href="aggrega
 tor2.html" title="Aggregator2">Aggregate</a> page for more details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>strategyMethodName</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.12:</b> This option can be used to explicit declare the method name to use, when using POJOs as the <tt>AggregationStrategy</tt>. See the <a shape="rect" href="aggregator2.html" title="Aggregator2">Aggregate</a> page for more details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>strategyMethodAllowNull</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.12:</b> If this option is <tt>false</tt> then the aggregate method is not used if there was no data to enrich. If this option is <tt>true</tt> then <tt>null</tt> values is used as the <tt>oldExchange</tt> (when no data to enrich), when using P
 OJOs as the <tt>AggregationStrategy</tt>. See the <a shape="rect" href="aggregator2.html" title="Aggregator2">Aggregate</a> page for more details. </td></tr><tr><td colspan="1" rowspan="1" class="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 sending messages to the multicasts occurs concurrently. Note the caller thread will still wait until all messages has been fully processed, before it continues. Its only the sending and processing the replies from the multicasts which happens concurrently. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>executorServiceRef</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</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 will send the message to all multicasts 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 process replies out-of-order, eg in the order they come back. If disabled, Camel will process replies in the same order as multicasted. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>timeout</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</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="multicast.html" title="Multicast">Multicast</a> hasn't been able to send and process all replies within the given timeframe, then the timeout triggers and the <a shape="rect" href="multicast.html" title="Multicast">Multicast</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 invoke
 d 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">&#160;</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 copy of the <a shape="rect" href="exchange.html" title="Exchange">Exchange</a> each multicast will receive. 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 the same option on <a shape="rect" href="splitter.html" title="Splitter">Splitter</a> for more details. </td></tr></tbody></table>
 </div>
 </div>
 
@@ -4659,7 +4705,7 @@ from("activemq:My.Queue").
 <h3><a shape="rect" name="BookPatternAppendix-EnrichOptions"></a>Enrich 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>uri</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> The endpoint uri for the external service to enrich from. You must use either <tt>uri</tt> or <tt>ref</tt>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>ref</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> Refers to the endpoint for the external service to enrich from. You must use either <tt>uri</tt> or <tt>ref</tt>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>strategyRef</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td cols
 pan="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 merge the reply from the external service, into a single outgoing message. By default Camel will use the reply from the external service as outgoing message. From <b>Camel 2.12</b> onwards you can also use a POJO as the <tt>AggregationStrategy</tt>, see the <a shape="rect" href="aggregator2.html" title="Aggregator2">Aggregate</a> page for more details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>strategyMethodName</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.12:</b> This option can be used to explicit declare the method name to use, when using POJOs as the <tt>AggregationStrategy</tt>. See the <a shape="rect" href="aggrega
 tor2.html" title="Aggregator2">Aggregate</a> page 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>uri</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> The endpoint uri for the external service to enrich from. You must use either <tt>uri</tt> or <tt>ref</tt>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>ref</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> Refers to the endpoint for the external service to enrich from. You must use either <tt>uri</tt> or <tt>ref</tt>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>strategyRef</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td cols
 pan="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 merge the reply from the external service, into a single outgoing message. By default Camel will use the reply from the external service as outgoing message. From <b>Camel 2.12</b> onwards you can also use a POJO as the <tt>AggregationStrategy</tt>, see the <a shape="rect" href="aggregator2.html" title="Aggregator2">Aggregate</a> page for more details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>strategyMethodName</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.12:</b> This option can be used to explicit declare the method name to use, when using POJOs as the <tt>AggregationStrategy</tt>. See the <a shape="rect" href="aggrega
 tor2.html" title="Aggregator2">Aggregate</a> page for more details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>strategyMethodAllowNull</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.12:</b> If this option is <tt>false</tt> then the aggregate method is not used if there was no data to enrich. If this option is <tt>true</tt> then <tt>null</tt> values is used as the <tt>oldExchange</tt> (when no data to enrich), when using POJOs as the <tt>AggregationStrategy</tt>. See the <a shape="rect" href="aggregator2.html" title="Aggregator2">Aggregate</a> page for more details. </td></tr></tbody></table>
 </div>
 </div>
 
@@ -4755,7 +4801,7 @@ from("direct:start")
 <h3><a shape="rect" name="BookPatternAppendix-PollEnrichOptions"></a>PollEnrich 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>uri</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> The endpoint uri for the external service to enrich from. You must use either <tt>uri</tt> or <tt>ref</tt>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>ref</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> Refers to the endpoint for the external service to enrich from. You must use either <tt>uri</tt> or <tt>ref</tt>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>strategyRef</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td cols
 pan="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 merge the reply from the external service, into a single outgoing message. By default Camel will use the reply from the external service as outgoing message. From <b>Camel 2.12</b> onwards you can also use a POJO as the <tt>AggregationStrategy</tt>, see the <a shape="rect" href="aggregator2.html" title="Aggregator2">Aggregate</a> page for more details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>strategyMethodName</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.12:</b> This option can be used to explicit declare the method name to use, when using POJOs as the <tt>AggregationStrategy</tt>. See the <a shape="rect" href="aggrega
 tor2.html" title="Aggregator2">Aggregate</a> page for more details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>timeout</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>-1</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Timeout in millis when polling from the external service. See below for important details about the timeout. </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>uri</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> The endpoint uri for the external service to enrich from. You must use either <tt>uri</tt> or <tt>ref</tt>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>ref</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> Refers to the endpoint for the external service to enrich from. You must use either <tt>uri</tt> or <tt>ref</tt>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>strategyRef</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td cols
 pan="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 merge the reply from the external service, into a single outgoing message. By default Camel will use the reply from the external service as outgoing message. From <b>Camel 2.12</b> onwards you can also use a POJO as the <tt>AggregationStrategy</tt>, see the <a shape="rect" href="aggregator2.html" title="Aggregator2">Aggregate</a> page for more details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>strategyMethodName</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.12:</b> This option can be used to explicit declare the method name to use, when using POJOs as the <tt>AggregationStrategy</tt>. See the <a shape="rect" href="aggrega
 tor2.html" title="Aggregator2">Aggregate</a> page for more details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>strategyMethodAllowNull</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.12:</b> If this option is <tt>false</tt> then the aggregate method is not used if there was no data to enrich. If this option is <tt>true</tt> then <tt>null</tt> values is used as the <tt>oldExchange</tt> (when no data to enrich), when using POJOs as the <tt>AggregationStrategy</tt>. See the <a shape="rect" href="aggregator2.html" title="Aggregator2">Aggregate</a> page for more details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>timeout</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>-1</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Timeout in millis when polling from the external service. See below for important details about the tim
 eout. </td></tr></tbody></table>
 </div>
 </div>
 

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

Modified: websites/production/camel/content/content-enricher.html
==============================================================================
--- websites/production/camel/content/content-enricher.html (original)
+++ websites/production/camel/content/content-enricher.html Tue Aug 20 12:21:45 2013
@@ -163,7 +163,7 @@ from("activemq:My.Queue").
 <h3><a shape="rect" name="ContentEnricher-EnrichOptions"></a>Enrich 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>uri</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> The endpoint uri for the external service to enrich from. You must use either <tt>uri</tt> or <tt>ref</tt>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>ref</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> Refers to the endpoint for the external service to enrich from. You must use either <tt>uri</tt> or <tt>ref</tt>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>strategyRef</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td cols
 pan="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 merge the reply from the external service, into a single outgoing message. By default Camel will use the reply from the external service as outgoing message. From <b>Camel 2.12</b> onwards you can also use a POJO as the <tt>AggregationStrategy</tt>, see the <a shape="rect" href="aggregator2.html" title="Aggregator2">Aggregate</a> page for more details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>strategyMethodName</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.12:</b> This option can be used to explicit declare the method name to use, when using POJOs as the <tt>AggregationStrategy</tt>. See the <a shape="rect" href="aggrega
 tor2.html" title="Aggregator2">Aggregate</a> page 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>uri</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> The endpoint uri for the external service to enrich from. You must use either <tt>uri</tt> or <tt>ref</tt>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>ref</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> Refers to the endpoint for the external service to enrich from. You must use either <tt>uri</tt> or <tt>ref</tt>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>strategyRef</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td cols
 pan="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 merge the reply from the external service, into a single outgoing message. By default Camel will use the reply from the external service as outgoing message. From <b>Camel 2.12</b> onwards you can also use a POJO as the <tt>AggregationStrategy</tt>, see the <a shape="rect" href="aggregator2.html" title="Aggregator2">Aggregate</a> page for more details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>strategyMethodName</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.12:</b> This option can be used to explicit declare the method name to use, when using POJOs as the <tt>AggregationStrategy</tt>. See the <a shape="rect" href="aggrega
 tor2.html" title="Aggregator2">Aggregate</a> page for more details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>strategyMethodAllowNull</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.12:</b> If this option is <tt>false</tt> then the aggregate method is not used if there was no data to enrich. If this option is <tt>true</tt> then <tt>null</tt> values is used as the <tt>oldExchange</tt> (when no data to enrich), when using POJOs as the <tt>AggregationStrategy</tt>. See the <a shape="rect" href="aggregator2.html" title="Aggregator2">Aggregate</a> page for more details. </td></tr></tbody></table>
 </div>
 </div>
 
@@ -259,7 +259,7 @@ from("direct:start")
 <h3><a shape="rect" name="ContentEnricher-PollEnrichOptions"></a>PollEnrich 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>uri</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> The endpoint uri for the external service to enrich from. You must use either <tt>uri</tt> or <tt>ref</tt>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>ref</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> Refers to the endpoint for the external service to enrich from. You must use either <tt>uri</tt> or <tt>ref</tt>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>strategyRef</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td cols
 pan="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 merge the reply from the external service, into a single outgoing message. By default Camel will use the reply from the external service as outgoing message. From <b>Camel 2.12</b> onwards you can also use a POJO as the <tt>AggregationStrategy</tt>, see the <a shape="rect" href="aggregator2.html" title="Aggregator2">Aggregate</a> page for more details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>strategyMethodName</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.12:</b> This option can be used to explicit declare the method name to use, when using POJOs as the <tt>AggregationStrategy</tt>. See the <a shape="rect" href="aggrega
 tor2.html" title="Aggregator2">Aggregate</a> page for more details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>timeout</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>-1</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Timeout in millis when polling from the external service. See below for important details about the timeout. </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>uri</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> The endpoint uri for the external service to enrich from. You must use either <tt>uri</tt> or <tt>ref</tt>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>ref</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> Refers to the endpoint for the external service to enrich from. You must use either <tt>uri</tt> or <tt>ref</tt>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>strategyRef</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td cols
 pan="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 merge the reply from the external service, into a single outgoing message. By default Camel will use the reply from the external service as outgoing message. From <b>Camel 2.12</b> onwards you can also use a POJO as the <tt>AggregationStrategy</tt>, see the <a shape="rect" href="aggregator2.html" title="Aggregator2">Aggregate</a> page for more details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>strategyMethodName</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.12:</b> This option can be used to explicit declare the method name to use, when using POJOs as the <tt>AggregationStrategy</tt>. See the <a shape="rect" href="aggrega
 tor2.html" title="Aggregator2">Aggregate</a> page for more details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>strategyMethodAllowNull</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.12:</b> If this option is <tt>false</tt> then the aggregate method is not used if there was no data to enrich. If this option is <tt>true</tt> then <tt>null</tt> values is used as the <tt>oldExchange</tt> (when no data to enrich), when using POJOs as the <tt>AggregationStrategy</tt>. See the <a shape="rect" href="aggregator2.html" title="Aggregator2">Aggregate</a> page for more details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>timeout</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>-1</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Timeout in millis when polling from the external service. See below for important details about the tim
 eout. </td></tr></tbody></table>
 </div>
 </div>
 

Modified: websites/production/camel/content/multicast.html
==============================================================================
--- websites/production/camel/content/multicast.html (original)
+++ websites/production/camel/content/multicast.html Tue Aug 20 12:21:45 2013
@@ -91,7 +91,7 @@
 <h3><a shape="rect" name="Multicast-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">&#160;</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 multicasts, into a single outgoing message from the <a shape="rect" href="multicast.html" title="Multicast">Multicast</a>. By default Camel will use the last reply as the outgoing message.  From <b>Camel 2.12</b> onwards you can also use a POJO as the <tt>AggregationStrategy</tt>, see the <a shape="rect" href="aggrega
 tor2.html" title="Aggregator2">Aggregate</a> page for more details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>strategyMethodName</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.12:</b> This option can be used to explicit declare the method name to use, when using POJOs as the <tt>AggregationStrategy</tt>. See the <a shape="rect" href="aggregator2.html" title="Aggregator2">Aggregate</a> page for more details. </td></tr><tr><td colspan="1" rowspan="1" class="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 sending messages to the multicasts occurs concurrently. Note the caller thread will still wait until all messages has been fully processed, before it continues. Its only the sending and processing the replies from the multicasts which happens 
 concurrently. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>executorServiceRef</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</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 will send the message to all multicasts regardless if one of them failed. You can deal with exceptions in the <a shape="rect" class="external-link" href="http://camel.apa
 che.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 process replies out-of-order, eg in the order they come back. If disabled, Camel will process replies in the same order as multicasted. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>timeout</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</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="multicast.html" title="Multicast">Multicast</a> hasn't been able to send and process all replies within the given timeframe, then the timeout triggers and the 
 <a shape="rect" href="multicast.html" title="Multicast">Multicast</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">&#160;</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 th
 e copy of the <a shape="rect" href="exchange.html" title="Exchange">Exchange</a> each multicast will receive. 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 the same option on <a shape="rect" href="splitter.html" title="Splitter">Splitter</a> 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">&#160;</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 multicasts, into a single outgoing message from the <a shape="rect" href="multicast.html" title="Multicast">Multicast</a>. By default Camel will use the last reply as the outgoing message.  From <b>Camel 2.12</b> onwards you can also use a POJO as the <tt>AggregationStrategy</tt>, see the <a shape="rect" href="aggrega
 tor2.html" title="Aggregator2">Aggregate</a> page for more details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>strategyMethodName</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.12:</b> This option can be used to explicit declare the method name to use, when using POJOs as the <tt>AggregationStrategy</tt>. See the <a shape="rect" href="aggregator2.html" title="Aggregator2">Aggregate</a> page for more details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>strategyMethodAllowNull</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.12:</b> If this option is <tt>false</tt> then the aggregate method is not used if there was no data to enrich. If this option is <tt>true</tt> then <tt>null</tt> values is used as the <tt>oldExchange</tt> (when no data to enrich), when using P
 OJOs as the <tt>AggregationStrategy</tt>. See the <a shape="rect" href="aggregator2.html" title="Aggregator2">Aggregate</a> page for more details. </td></tr><tr><td colspan="1" rowspan="1" class="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 sending messages to the multicasts occurs concurrently. Note the caller thread will still wait until all messages has been fully processed, before it continues. Its only the sending and processing the replies from the multicasts which happens concurrently. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>executorServiceRef</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</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 will send the message to all multicasts 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 process replies out-of-order, eg in the order they come back. If disabled, Camel will process replies in the same order as multicasted. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>timeout</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</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="multicast.html" title="Multicast">Multicast</a> hasn't been able to send and process all replies within the given timeframe, then the timeout triggers and the <a shape="rect" href="multicast.html" title="Multicast">Multicast</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 invoke
 d 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">&#160;</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 copy of the <a shape="rect" href="exchange.html" title="Exchange">Exchange</a> each multicast will receive. 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 the same option on <a shape="rect" href="splitter.html" title="Splitter">Splitter</a> for more details. </td></tr></tbody></table>
 </div>
 </div>
 



Mime
View raw message