{div:class=confluenceTableSmall}
|| Name || Default Value || Description ||
| {{delimiter}} | {{,}} | Delimiter used if the [_expression_] returned multiple endpoints. *Camel 2.13* can be disabled using "false" |
| {{strategyRef}} | | An [AggregationStrategy|http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/processor/aggregate/AggregationStrategy.html] that will assemble the replies from recipients into a single outgoing message from the [Recipient List]. By default Camel will use the last reply as the outgoing message. From *Camel 2.12* onwards you can also use a POJO as the {{AggregationStrategy}}, see the [Aggregate|Aggregator2] page for more details. |
| {{strategyMethodName}} | | *Camel 2.12:* This option can be used to explicit declare the method name to use, when using POJOs as the {{AggregationStrategy}}. See the [Aggregate|Aggregator2] page for more details. |
| {{strategyMethodAllowNull}} | {{false}} | *Camel 2.12:* If this option is {{false}} then the aggregate method is not used if there was no data to enrich. If this option is {{true}} then {{null}} values is used as the {{oldExchange}} (when no data to enrich), when using POJOs as the {{AggregationStrategy}}. See the [Aggregate|Aggregator2] page for more details. |
| {{parallelProcessing}} | {{false}} | *Camel 2.2:* 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. |
| {{parallelAggregate}} | {{false}} | *Camel 2.14:* If enabled then the {{aggregate}} method on {{AggregationStrategy}} can be called concurrently. Notice that this would require the implementation of {{AggregationStrategy}} to be implemented as thread-safe. By default this is {{false}} meaning that Camel synchronizes the call to the {{aggregate}} method. Though in some use-cases this can be used to archive higher performance when the {{AggregationStrategy}} is implemented as thread-safe. |
| {{executorServiceRef}} | | *Camel 2.2:* A custom [Thread Pool|Threading Model] to use for parallel processing. Note that enabling this option implies parallel processing, so you need not enable that option as well. |
| {{stopOnException}} | {{false}} | *Camel 2.2:* 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 [AggregationStrategy|http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/processor/aggregate/AggregationStrategy.html] implementation, which supports full control of error handling. |
| {{ignoreInvalidEndpoints}} | {{false}} | *Camel 2.3:* Whether to ignore an endpoint URI that could not be resolved. If disabled, Camel will throw an exception identifying the invalid endpoint URI. |
| {{streaming}} | {{false}} | *Camel 2.5:* 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 [_expression_]. |
| {{timeout}} | | *Camel 2.5:* Specifies a processing timeout milliseconds. If the [Recipient List] hasn't been able to send and process all replies within this timeframe, then the timeout triggers and the [Recipient List] breaks out, with message flow continuing to the next element. Note that if you provide a [TimeoutAwareAggregationStrategy|http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/processor/aggregate/TimeoutAwareAggregationStrategy.html], its {{timeout}} method is invoked before breaking out. *Beware:* 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. |
| {{onPrepareRef}} | | *Camel 2.8:* A custom [Processor] to prepare the copy of the [Exchange] each recipient will receive. This allows you to perform arbitrary transformations, such as deep-cloning the message payload (or any other custom logic). |
| {{shareUnitOfWork}} | {{false}} | *Camel 2.8:* Whether the unit of work should be shared. See [the same option on Splitter|Splitter#Sharingunitofwork] for more details. |
| {{cacheSize}} | {{1000}} | *Camel 2.13.1/2.12.4:* Allows to configure the cache size for the {{ProducerCache}} which caches producers for reuse in the routing slip. Will by default use the default cache size which is 1000. Setting the value to -1 allows to turn off the cache all together. |
{div} |
