Author: buildbot
Date: Mon Mar 10 13:19:43 2014
New Revision: 900905
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/recipient-list.html
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/recipient-list.html
==============================================================================
--- websites/production/camel/content/recipient-list.html (original)
+++ websites/production/camel/content/recipient-list.html Mon Mar 10 13:19:43
2014
@@ -87,7 +87,7 @@
<tr>
<td valign="top" width="100%">
<div class="wiki-content maincontent"><h3
id="RecipientList-RecipientList">Recipient List</h3><p>The <a shape="rect"
class="external-link"
href="http://www.enterpriseintegrationpatterns.com/RecipientList.html";
rel="nofollow">Recipient List</a> from the <a shape="rect"
href="enterprise-integration-patterns.html">EIP patterns</a> allows you to
route messages to a number of dynamically specified recipients.</p><p><img
class="confluence-embedded-image confluence-external-resource"
src="http://www.enterpriseintegrationpatterns.com/img/RecipientList.gif";
data-image-src="http://www.enterpriseintegrationpatterns.com/img/RecipientList.gif";></p><p>The
recipients will receive a copy of the <strong>same</strong> <a shape="rect"
href="exchange.html">Exchange</a>, and Camel will execute them
sequentially.</p><h3 id="RecipientList-Options">Options</h3><div
class="confluenceTableSmall">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p> Default Value </p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>delimiter</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>,</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> Delimiter used if the <a
shape="rect" href="expression.html" title="Expression">Expression</a> returned
multiple endpoints. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>strategyRef</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> 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 recipients 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 <strong>Camel 2.12</strong> onwards you can
also use a POJO as the <code>AggregationStrategy</code>, see the <a
shape="rect" href="aggregator2.html" title="Aggregator2">Aggregate</a> page for
more details. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>strategyMethodName</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <strong>Camel 2.12:</strong> This option
can be used to explicit declare the method name to use, when using POJOs as the
<code>AggregationStrategy</code>. See the <a shape="rect"
href="aggregator2.html" title="Aggregator2">Aggregate</a> page for more
details. </p></td></tr><tr><td colspan
="1" rowspan="1" class="confluenceTd"><p> <code>strategyMethodAllowNull</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>false</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>Camel 2.12:</strong> If this option is
<code>false</code> then the aggregate method is not used if there was no data
to enrich. If this option is <code>true</code> then <code>null</code> values is
used as the <code>oldExchange</code> (when no data to enrich), when using POJOs
as the <code>AggregationStrategy</code>. See the <a shape="rect"
href="aggregator2.html" title="Aggregator2">Aggregate</a> page for more
details. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>parallelProcessing</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <strong>Camel 2.2:</strong> If enabled,
messages are sent to the recipients concurrently. Note tha
t 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. </p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>executorServiceRef</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.2:</strong> 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.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>stopOnException</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <strong>Camel 2.2:</strong> Whether to
immediately stop processing when an e
xception 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.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>ignoreInvalidEndpoints</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <strong>Camel 2.3:</strong> Whether to
ignore an endpoint URI that could not be resolved. If disabled, Camel will
throw an exception identifying the invalid endpoint URI. </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>streaming</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>false</code> </
p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel
2.5:</strong> 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>. </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>timeout</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.5:</strong>
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. Not
e 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 <code>timeout</code> method is invoked before breaking out.
<strong>Beware:</strong> 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.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>onPrepareRef</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>Camel 2.8:</strong> A custom <a shape="rect"
href="processor.html" title="Processor">Processor</a> to prepare the copy of
the <a shape="rect" href="exchange.h
tml" 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). </p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>shareUnitOfWork</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel
2.8:</strong> 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. </p></td></tr></tbody></table>
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p> Default Value </p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>delimiter</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>,</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> Delimiter used if the <a
shape="rect" href="expression.html" title="Expression">Expression</a> returned
multiple endpoints. <strong>Camel 2.13</strong> can be disabled using "false"
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>strategyRef</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> 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 recipients 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 <strong>Camel 2.12</strong> onwards you can also use a
POJO as the <code>AggregationStrategy</code>, see the <a shape="rect"
href="aggregator2.html" title="Aggregator2">Aggregate</a> page for more
details. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>strategyMethodName</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>Camel 2.12:</strong> This option can be used
to explicit declare the method name to use, when using POJOs as the
<code>AggregationStrategy</code>. See the <a shape="rect"
href="aggregator2.html" title="Aggregator2">Aggregat
e</a> page for more details. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>strategyMethodAllowNull</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel
2.12:</strong> If this option is <code>false</code> then the aggregate method
is not used if there was no data to enrich. If this option is <code>true</code>
then <code>null</code> values is used as the <code>oldExchange</code> (when no
data to enrich), when using POJOs as the <code>AggregationStrategy</code>. See
the <a shape="rect" href="aggregator2.html" title="Aggregator2">Aggregate</a>
page for more details. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>parallelProcessing</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel
2.2:</strong> 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. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>executorServiceRef</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <strong>Camel 2.2:</strong> 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.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>stopOnException</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <strong>Camel 2.2:
</strong> 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.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>ignoreInvalidEndpoints</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <strong>Camel 2.3:</strong> Whether to
ignore an endpoint URI that could not be resolved. If disabled, Camel will
throw an exception identifying the invalid endpoint URI. </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>streaming</code>
</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.5:</strong> 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>. </p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>timeout</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <strong>Camel 2.5:</strong> 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 <code>timeout</code> method is invoked before breaking out.
<strong>Beware:</strong> 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.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>onPrepareRef</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>Camel 2.8:</strong> A custom <a shape="rect"
href="processor.html" title="Processor">Processor</a> t
o 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). </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>shareUnitOfWork</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.8:</strong>
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. </p></td></tr></tbody></table>
</div><h4 id="RecipientList-StaticRecipientList">Static Recipient
List</h4><p>The following example shows how to route a request from an input
<strong>queue:a</strong> endpoint to a static list of
destinations</p><p><strong>Using Annotations</strong><br clear="none"> You can
use the <a shape="rect" href="recipientlist-annotation.html">RecipientList
Annotation</a> on a POJO to create a Dynamic Recipient List. For more details
see the <a shape="rect" href="bean-integration.html">Bean
Integration</a>.</p><p><strong>Using the <a shape="rect"
href="fluent-builders.html">Fluent Builders</a></strong></p><div class="code
panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><
![http://www.enterpriseintegrationpatterns.com/img/RecipientList.gif"](http://www.enterpriseintegrationpatterns.com/img/RecipientList.gif"){kind=link}