Modified: websites/production/camel/content/camel-2120-release.html
==============================================================================
--- websites/production/camel/content/camel-2120-release.html (original)
+++ websites/production/camel/content/camel-2120-release.html Tue Aug 20
08:19:47 2013
@@ -94,7 +94,7 @@
<p>Welcome to the 2.12.0 release which approx XXX issues resolved (new
features, improvements and bug fixes such as...)</p>
-<ul><li><a shape="rect" href="endpoint-annotations.html" title="Endpoint
Annotations">Endpoint Annotations</a> along with automatically created HTML
documentation for the endpoint parameters; this makes it easier for component
developers to add a few refactoring-safe annotations to their Endpoint or
Consumer implementations and, (along with javadoc comments on the field or
setter method), get nice user documentation on how to use the endpoint for
free.</li><li><a shape="rect" href="componentconfiguration.html"
title="ComponentConfiguration">ComponentConfiguration</a> API provides a handy
API for tools developers to introspect on a Component to find all the possible
parameters, their types and any extra annotations (like Bean Validation
Annotations) to be able to create/edit endpoints or URI strings so that tools
can generate nicer UIs for configuring endpoints than just letting folks edit
Strings.</li><li><a shape="rect" href="endpointcompleter.html"
title="EndpointCompleter">Endpoi
ntCompleter</a> API provides a hook so that command line tools (like <a
shape="rect" class="external-link"
href="http://karaf.apache.org/manual/latest-2.3.x/users-guide/using-console.html";>Karaf's
shell</a>), IDEs and web tools can get (bash tab like) auto-completion on
endpoint paths (such as file or directory names, message queue names, database
table names) when creating or using new endpoints</li><li>Reduced stack-frames
in use during routing, that also makes Camel's stack traces being logged much
less verbose. This also allows people to easier debug the internals of Camel as
less <tt>AsyncCallback</tt> callbacks are in use during routing.</li><li>Easy
to use <a shape="rect" href="message-history.html" title="Message
History">Message History</a> out of the box. And included message history as
"route stack-trace" when exceptions logged by <a shape="rect"
href="error-handler.html" title="Error Handler">Error Handler</a> to make it
easier for end users to spot where the exception o
ccurred.</li><li><a shape="rect" href="spring-web-services.html" title="Spring
Web Services">Spring Web Services</a> now supports setting/receiving SOAP
headers more easily using a header on the Camel <a shape="rect"
href="message.html" title="Message">Message</a>.</li><li>Evaluating <a
shape="rect" href="groovy.html" title="Groovy">Groovy</a> expressions is faster
as we cache the compiled scripts.</li><li>Added <tt>base64</tt> option to <a
shape="rect" href="shiro-security.html" title="Shiro Security">Shiro
Security</a> to allow transferring security token over <a shape="rect"
href="jms.html" title="JMS">JMS</a> and other transports as base64 encoded
representation.</li><li>Made it easier to use <a shape="rect"
href="shiro-security.html" title="Shiro Security">Shiro Security</a> as the
credentials can be provided in headers, when sending a message to a secured
route.</li><li><a shape="rect" href="bindy.html" title="Bindy">Bindy</a> now
supports enums.</li><li>Added new <a shape="re
ct" href="backlogdebugger.html" title="BacklogDebugger">BacklogDebugger</a> to
perform live debugging of messages during routing. The <a shape="rect"
href="backlogdebugger.html" title="BacklogDebugger">BacklogDebugger</a> has JMX
API allows tooling to control the debugger.</li><li>While using the <a
shape="rect" class="external-link"
href="http://xircles.codehaus.org/projects/jackson"; rel="nofollow">Jackson
library</a> through the <a shape="rect" href="json.html" title="JSON">JSON</a>
Dataformat there's now a <tt>jsonView</tt> attribute you could make use of
directly inside the <a shape="rect" href="dsl.html" title="DSL">DSL</a>
itself.</li><li><a shape="rect" href="smpp.html" title="SMPP">SMPP</a> now
supports optional parameters in all commands where they are
possible.</li><li><a shape="rect" href="jdbc.html" title="JDBC">JDBC</a> now
supports named parameters.</li><li>Added timeout support for <a shape="rect"
href="direct.html" title="Direct">Direct</a> producers to wait for cons
umer to become active.</li><li>Added <tt>stats</tt> action to <a shape="rect"
href="controlbus.html" title="ControlBus">ControlBus</a> to easily get
performance statics in a single XML message.</li><li>Added support for request
timeout on <a shape="rect" href="netty.html" title="Netty">Netty</a> producer,
and to configure logging level on <a shape="rect" href="netty.html"
title="Netty">Netty</a> consumer to be less noisy for ChannelClosedException
which can flood the logs when client disconnects abruptly.</li><li><a
shape="rect" href="springbatch.html" title="SpringBatch">Spring Batch</a>
component producer now returns the <tt>JobExecution</tt> instance as the output
message. Users can use the <tt>JobExecution</tt> instance to perform some
operations using the Spring Batch API directly.</li><li>Added support for NULL
values in <a shape="rect" href="sql-component.html" title="SQL
Component">SQL</a> with named parameters.</li><li>Optimized <a shape="rect"
href="jetty.html" title="Jett
y">Jetty</a> streaming responses in non-chunked mode; and as well using buffer
sizes based on <tt>HttpServletResponse.getBufferSize()</tt> instead of fixed
size of 4kb.</li><li>Added <tt>greedy</tt> option to <a shape="rect"
href="polling-consumer.html" title="Polling Consumer">scheduled polling
consumer</a>.</li><li>Added support for accessing the length field on Java
arrays in <a shape="rect" href="simple.html" title="Simple">Simple</a>
language.</li><li>Added support for using JAXB annotations with Camel's Jackson
<a shape="rect" href="json.html" title="JSON">JSON</a> component.</li><li>Added
the ability for <a shape="rect" href="bindy.html" title="Bindy">Bindy</a> to
skip content when parsing fixed-length records.</li><li><a shape="rect"
href="mongodb.html" title="MongoDB">MongoDB</a> now supports aggregation
queries.</li><li><a shape="rect" href="netty.html" title="Netty">Netty</a>
allows to use shared Netty boss and worker thread pools.</li><li>The <a
shape="rect" href="camel-
maven-archetypes.html" title="Camel Maven Archetypes">Camel Maven
Archetypes</a> for component and data format now packages as OSGi bundles out
of the box.</li><li>Easier <a shape="rect" href="stream-caching.html"
title="Stream caching">Stream caching</a> configuration using
<tt>StreamCachingStrategy</tt>. Also allows spool directory per <a shape="rect"
href="camelcontext.html" title="CamelContext">CamelContext</a> instead of
shared per JVM. And insight at runtime using JMX management. As well allowing
to plugin 3rd party implementations.</li><li>Improved <a shape="rect"
href="netty.html" title="Netty">Netty</a> to be able to join an UDP multicast
group.</li><li>Using Camel <a shape="rect" href="spring.html"
title="Spring">Spring</a> is now setting up Camel routes later in the process
allow Spring to complete all of its dependency injection, before Camel
<tt>RouteBuilder</tt> instances is configured. This allows to safely use Spring
dependency injection in these <tt>RouteBuilder</tt
> classes.</li><li>Services in a <a shape="rect" href="camelcontext.html"
> title="CamelContext">CamelContext</a> which can only be enlisted once (eg it
> similar to a static in a JVM) has simpler and fixed MBean names in
> JMX.</li><li><a shape="rect" href="sql-component.html" title="SQL
> Component">JDBC based aggregation repository</a> for the <a shape="rect"
> href="aggregator2.html" title="Aggregator2">Aggregate</a> EIP now supports
> optimistic locking, allows clustered Camel applications to use a shared
> database for the aggregation repository.</li><li><a shape="rect"
> href="recipient-list.html" title="Recipient List">Recipient List</a> stores
> a property (<tt>Exchange.RECIPIENT_LIST_ENDPOINT</tt>) on the <a
> shape="rect" href="exchange.html" title="Exchange">Exchange</a> with the <a
> shape="rect" href="uris.html" title="URIs">URIs</a> of the <a shape="rect"
> href="endpoint.html" title="Endpoint">Endpoint</a> the message was sent
> to.</li><li>Added <tt>mask</tt> option to <a shape="rect" href="
camel-jmx.html" title="Camel JMX">Camel JMX</a> to hide sensitive information
such as passwords.</li><li>Added <tt>outputType</tt> option supporting
<tt>SelectList</tt>, and <tt>SelectOne</tt> to <a shape="rect"
href="sql-component.html" title="SQL Component">SQL Component</a> to dictate
the output message body type when doing SQL SELECT queries.</li><li><a
shape="rect" href="polling-consumer.html" title="Polling Consumer">Polling
Consumer</a>s such as <a shape="rect" href="file2.html" title="File2">File</a>,
and <a shape="rect" href="ftp2.html" title="FTP2">FTP</a> now supports using
custom scheduler. Providing a new <a shape="rect" href="quartz2.html"
title="Quartz2">Quartz2</a>, and <a shape="rect" href="spring.html"
title="Spring">Spring</a> based out of the box, that allows to use CRON based
scheduler.</li><li><a shape="rect" href="polling-consumer.html" title="Polling
Consumer">Polling Consumer</a>s such as <a shape="rect" href="file2.html"
title="File2">File</a>, and <a shape
="rect" href="ftp2.html" title="FTP2">FTP</a> now supports <em>backoff</em>,
to let the consumer be less aggressive, when there has been no messages to
poll, or errors keeps occurring for a while.</li><li>Added support for XML
Encryption 1.1 algorithms in the <a shape="rect"
href="xmlsecurity-dataformat.html" title="XMLSecurity DataFormat">XMLSecurity
data format</a>. It is now possible to specify stronger digest algorithms when
using RSA OAEP Key Transport algorithms.</li><li><a shape="rect"
href="netty.html" title="Netty">Netty</a> consumer now unbinds/binds the
acceptor when the route is suspended/resumed.</li></ul>
+<ul><li><a shape="rect" href="endpoint-annotations.html" title="Endpoint
Annotations">Endpoint Annotations</a> along with automatically created HTML
documentation for the endpoint parameters; this makes it easier for component
developers to add a few refactoring-safe annotations to their Endpoint or
Consumer implementations and, (along with javadoc comments on the field or
setter method), get nice user documentation on how to use the endpoint for
free.</li><li><a shape="rect" href="componentconfiguration.html"
title="ComponentConfiguration">ComponentConfiguration</a> API provides a handy
API for tools developers to introspect on a Component to find all the possible
parameters, their types and any extra annotations (like Bean Validation
Annotations) to be able to create/edit endpoints or URI strings so that tools
can generate nicer UIs for configuring endpoints than just letting folks edit
Strings.</li><li><a shape="rect" href="endpointcompleter.html"
title="EndpointCompleter">Endpoi
ntCompleter</a> API provides a hook so that command line tools (like <a
shape="rect" class="external-link"
href="http://karaf.apache.org/manual/latest-2.3.x/users-guide/using-console.html";>Karaf's
shell</a>), IDEs and web tools can get (bash tab like) auto-completion on
endpoint paths (such as file or directory names, message queue names, database
table names) when creating or using new endpoints</li><li>Reduced stack-frames
in use during routing, that also makes Camel's stack traces being logged much
less verbose. This also allows people to easier debug the internals of Camel as
less <tt>AsyncCallback</tt> callbacks are in use during routing.</li><li>Easy
to use <a shape="rect" href="message-history.html" title="Message
History">Message History</a> out of the box. And included message history as
"route stack-trace" when exceptions logged by <a shape="rect"
href="error-handler.html" title="Error Handler">Error Handler</a> to make it
easier for end users to spot where the exception o
ccurred.</li><li><a shape="rect" href="spring-web-services.html" title="Spring
Web Services">Spring Web Services</a> now supports setting/receiving SOAP
headers more easily using a header on the Camel <a shape="rect"
href="message.html" title="Message">Message</a>.</li><li>Evaluating <a
shape="rect" href="groovy.html" title="Groovy">Groovy</a> expressions is faster
as we cache the compiled scripts.</li><li>Added <tt>base64</tt> option to <a
shape="rect" href="shiro-security.html" title="Shiro Security">Shiro
Security</a> to allow transferring security token over <a shape="rect"
href="jms.html" title="JMS">JMS</a> and other transports as base64 encoded
representation.</li><li>Made it easier to use <a shape="rect"
href="shiro-security.html" title="Shiro Security">Shiro Security</a> as the
credentials can be provided in headers, when sending a message to a secured
route.</li><li><a shape="rect" href="bindy.html" title="Bindy">Bindy</a> now
supports enums.</li><li>Added new <a shape="re
ct" href="backlogdebugger.html" title="BacklogDebugger">BacklogDebugger</a> to
perform live debugging of messages during routing. The <a shape="rect"
href="backlogdebugger.html" title="BacklogDebugger">BacklogDebugger</a> has JMX
API allows tooling to control the debugger.</li><li>While using the <a
shape="rect" class="external-link"
href="http://xircles.codehaus.org/projects/jackson"; rel="nofollow">Jackson
library</a> through the <a shape="rect" href="json.html" title="JSON">JSON</a>
Dataformat there's now a <tt>jsonView</tt> attribute you could make use of
directly inside the <a shape="rect" href="dsl.html" title="DSL">DSL</a>
itself.</li><li><a shape="rect" href="smpp.html" title="SMPP">SMPP</a> now
supports optional parameters in all commands where they are
possible.</li><li><a shape="rect" href="jdbc.html" title="JDBC">JDBC</a> now
supports named parameters.</li><li>Added timeout support for <a shape="rect"
href="direct.html" title="Direct">Direct</a> producers to wait for cons
umer to become active.</li><li>Added <tt>stats</tt> action to <a shape="rect"
href="controlbus.html" title="ControlBus">ControlBus</a> to easily get
performance statics in a single XML message.</li><li>Added support for request
timeout on <a shape="rect" href="netty.html" title="Netty">Netty</a> producer,
and to configure logging level on <a shape="rect" href="netty.html"
title="Netty">Netty</a> consumer to be less noisy for ChannelClosedException
which can flood the logs when client disconnects abruptly.</li><li><a
shape="rect" href="springbatch.html" title="SpringBatch">Spring Batch</a>
component producer now returns the <tt>JobExecution</tt> instance as the output
message. Users can use the <tt>JobExecution</tt> instance to perform some
operations using the Spring Batch API directly.</li><li>Added support for NULL
values in <a shape="rect" href="sql-component.html" title="SQL
Component">SQL</a> with named parameters.</li><li>Optimized <a shape="rect"
href="jetty.html" title="Jett
y">Jetty</a> streaming responses in non-chunked mode; and as well using buffer
sizes based on <tt>HttpServletResponse.getBufferSize()</tt> instead of fixed
size of 4kb.</li><li>Added <tt>greedy</tt> option to <a shape="rect"
href="polling-consumer.html" title="Polling Consumer">scheduled polling
consumer</a>.</li><li>Added support for accessing the length field on Java
arrays in <a shape="rect" href="simple.html" title="Simple">Simple</a>
language.</li><li>Added support for using JAXB annotations with Camel's Jackson
<a shape="rect" href="json.html" title="JSON">JSON</a> component.</li><li>Added
the ability for <a shape="rect" href="bindy.html" title="Bindy">Bindy</a> to
skip content when parsing fixed-length records.</li><li><a shape="rect"
href="mongodb.html" title="MongoDB">MongoDB</a> now supports aggregation
queries.</li><li><a shape="rect" href="netty.html" title="Netty">Netty</a>
allows to use shared Netty boss and worker thread pools.</li><li>The <a
shape="rect" href="camel-
maven-archetypes.html" title="Camel Maven Archetypes">Camel Maven
Archetypes</a> for component and data format now packages as OSGi bundles out
of the box.</li><li>Easier <a shape="rect" href="stream-caching.html"
title="Stream caching">Stream caching</a> configuration using
<tt>StreamCachingStrategy</tt>. Also allows spool directory per <a shape="rect"
href="camelcontext.html" title="CamelContext">CamelContext</a> instead of
shared per JVM. And insight at runtime using JMX management. As well allowing
to plugin 3rd party implementations.</li><li>Improved <a shape="rect"
href="netty.html" title="Netty">Netty</a> to be able to join an UDP multicast
group.</li><li>Using Camel <a shape="rect" href="spring.html"
title="Spring">Spring</a> is now setting up Camel routes later in the process
allow Spring to complete all of its dependency injection, before Camel
<tt>RouteBuilder</tt> instances is configured. This allows to safely use Spring
dependency injection in these <tt>RouteBuilder</tt
> classes.</li><li>Services in a <a shape="rect" href="camelcontext.html"
> title="CamelContext">CamelContext</a> which can only be enlisted once (eg it
> similar to a static in a JVM) has simpler and fixed MBean names in
> JMX.</li><li><a shape="rect" href="sql-component.html" title="SQL
> Component">JDBC based aggregation repository</a> for the <a shape="rect"
> href="aggregator2.html" title="Aggregator2">Aggregate</a> EIP now supports
> optimistic locking, allows clustered Camel applications to use a shared
> database for the aggregation repository.</li><li><a shape="rect"
> href="recipient-list.html" title="Recipient List">Recipient List</a> stores
> a property (<tt>Exchange.RECIPIENT_LIST_ENDPOINT</tt>) on the <a
> shape="rect" href="exchange.html" title="Exchange">Exchange</a> with the <a
> shape="rect" href="uris.html" title="URIs">URIs</a> of the <a shape="rect"
> href="endpoint.html" title="Endpoint">Endpoint</a> the message was sent
> to.</li><li>Added <tt>mask</tt> option to <a shape="rect" href="
camel-jmx.html" title="Camel JMX">Camel JMX</a> to hide sensitive information
such as passwords.</li><li>Added <tt>outputType</tt> option supporting
<tt>SelectList</tt>, and <tt>SelectOne</tt> to <a shape="rect"
href="sql-component.html" title="SQL Component">SQL Component</a> to dictate
the output message body type when doing SQL SELECT queries.</li><li><a
shape="rect" href="polling-consumer.html" title="Polling Consumer">Polling
Consumer</a>s such as <a shape="rect" href="file2.html" title="File2">File</a>,
and <a shape="rect" href="ftp2.html" title="FTP2">FTP</a> now supports using
custom scheduler. Providing a new <a shape="rect" href="quartz2.html"
title="Quartz2">Quartz2</a>, and <a shape="rect" href="spring.html"
title="Spring">Spring</a> based out of the box, that allows to use CRON based
scheduler.</li><li><a shape="rect" href="polling-consumer.html" title="Polling
Consumer">Polling Consumer</a>s such as <a shape="rect" href="file2.html"
title="File2">File</a>, and <a shape
="rect" href="ftp2.html" title="FTP2">FTP</a> now supports <em>backoff</em>,
to let the consumer be less aggressive, when there has been no messages to
poll, or errors keeps occurring for a while.</li><li>Added support for XML
Encryption 1.1 algorithms in the <a shape="rect"
href="xmlsecurity-dataformat.html" title="XMLSecurity DataFormat">XMLSecurity
data format</a>. It is now possible to specify stronger digest algorithms when
using RSA OAEP Key Transport algorithms.</li><li><a shape="rect"
href="netty.html" title="Netty">Netty</a> consumer now unbinds/binds the
acceptor when the route is suspended/resumed.</li><li><a shape="rect"
href="eip.html" title="EIP">EIP</a>s supporting <tt>AggregationStrategy</tt>
such as <a shape="rect" href="aggregator2.html"
title="Aggregator2">Aggregate</a>, <a shape="rect" href="splitter.html"
title="Splitter">Splitter</a>, <a shape="rect" href="content-enricher.html"
title="Content Enricher">Content Enricher</a> now supports using a POJO as the
<tt>
AggregationStrategy</tt>, which allows to implement the aggregate logic with
no Camel API dependency. See more details at the <a shape="rect"
href="aggregator2.html" title="Aggregator2">Aggregate</a> page.</li></ul>
<h3><a shape="rect" name="Camel2.12.0Release-FixedIssues"></a>Fixed Issues</h3>
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 08:19:47
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"> </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"> </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"> </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. </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"> </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"> </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"> </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"> </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>
</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"> </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"> </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"> </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. </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"> </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"> </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"> </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"> </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>
</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 08:19:47 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"> </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. </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"> </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> </t
d><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"> </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 i
n future Camel releases. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>onPrepareRef</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.8:</b> Refers to a custom <a shape="rect"
href="processor.html" title="Processor">Processor</a> to prepare the 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"> </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"> </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"> </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"> </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"> </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>
</div>
</div>
Modified: websites/production/camel/content/splitter.html
==============================================================================
--- websites/production/camel/content/splitter.html (original)
+++ websites/production/camel/content/splitter.html Tue Aug 20 08:19:47 2013
@@ -97,7 +97,7 @@
<h3><a shape="rect" name="Splitter-Options"></a>Options</h3>
<div class="confluenceTableSmall"><div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Name </th><th colspan="1" rowspan="1"
class="confluenceTh"> Default Value </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>strategyRef</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Refers to an <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/processor/aggregate/AggregationStrategy.html";>AggregationStrategy</a>
to be used to assemble the replies from the sub-messages, into a single
outgoing message from the <a shape="rect" href="splitter.html"
title="Splitter">Splitter</a>. See the defaults described below in <em><a
shape="rect" href="#Splitter-WhattheSplitterreturns">What the Splitter
returns</a></em>. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <
tt>parallelProcessing</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> If enabled then processing the sub-messages occurs
concurrently. Note the caller thread will still wait until all sub-messages has
been fully processed, before it continues. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>executorServiceRef</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1"
rowspan="1" class="confluenceTd"> Refers to a custom <a shape="rect"
href="threading-model.html" title="Threading Model">Thread Pool</a> to be used
for parallel processing. Notice if you set this option, then parallel
processing is automatically implied, and you do not have to enable that option
as well. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>stopOnException</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.2:</b> Whether or not to stop continue
processing immediately when an exception occurred. If disable, then Camel
continue splitting and process the sub-messages regardless if one of them
failed. You can deal with exceptions in the <a shape="rect"
class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/processor/aggregate/AggregationStrategy.html";>AggregationStrategy</a>
class where you have full control how to handle that. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>streaming</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> If enabled then Camel will split
in a streaming fashion, which means it will split the input message in chunks.
This reduces the memory overhead. For example if you split big messages its
recommended to enable streaming. If streaming is enabled then the sub-message
replies will be a
ggregated out-of-order, eg in the order they come back. If disabled, Camel
will process sub-message replies in the same order as they where splitted.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>timeout</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.5:</b> Sets a total timeout specified in
millis. If the <a shape="rect" href="recipient-list.html" title="Recipient
List">Recipient List</a> hasn't been able to split and process all replies
within the given timeframe, then the timeout triggers and the <a shape="rect"
href="splitter.html" title="Splitter">Splitter</a> breaks out and continues.
Notice if you provide a <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/processor/aggregate/TimeoutAwareAggregationStrategy.html";>TimeoutAwareAggregationStrategy</a>
then the <tt>timeout</tt> method is invoked before breakin
g out. If the timeout is reached with running tasks still remaining, certain
tasks for which it is difficult for Camel to shut down in a graceful manner may
continue to run. So use this option with a bit of care. We may be able to
improve this functionality in future Camel releases. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>onPrepareRef</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <b>Camel 2.8:</b> Refers to a custom <a
shape="rect" href="processor.html" title="Processor">Processor</a> to prepare
the sub-message of the <a shape="rect" href="exchange.html"
title="Exchange">Exchange</a>, before its processed. This allows you to do any
custom logic, such as deep-cloning the message payload if that's needed etc.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>shareUnitOfWork</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>false</tt> </td><td colspan=
"1" rowspan="1" class="confluenceTd"> <b>Camel 2.8:</b> Whether the unit of
work should be shared. See further below for more details.
</td></tr></tbody></table>
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Name </th><th colspan="1" rowspan="1"
class="confluenceTh"> Default Value </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>strategyRef</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Refers to an <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/processor/aggregate/AggregationStrategy.html";>AggregationStrategy</a>
to be used to assemble the replies from the sub-messages, into a single
outgoing message from the <a shape="rect" href="splitter.html"
title="Splitter">Splitter</a>. See the defaults described below in <em><a
shape="rect" href="#Splitter-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"> </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 col
span="1" rowspan="1" class="confluenceTd"> <tt>executorServiceRef</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td
colspan="1" rowspan="1" class="confluenceTd"> Refers to a custom <a
shape="rect" href="threading-model.html" title="Threading Model">Thread
Pool</a> to be used for parallel processing. Notice if you set this option,
then parallel processing is automatically implied, and you do not have to
enable that option as well. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>stopOnException</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.2:</b> Whether or not to stop continue
processing immediately when an exception occurred. If disable, then Camel
continue splitting and process the sub-messages regardless if one of them
failed. You can deal with exceptions in the <a shape="rect"
class="external-link" href="http://camel.apache.org/maven/current/c
amel-core/apidocs/org/apache/camel/processor/aggregate/AggregationStrategy.html">AggregationStrategy</a>
class where you have full control how to handle that. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>streaming</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> If enabled then Camel will split
in a streaming fashion, which means it will split the input message in chunks.
This reduces the memory overhead. For example if you split big messages its
recommended to enable streaming. If streaming is enabled then the sub-message
replies will be aggregated out-of-order, eg in the order they come back. If
disabled, Camel will process sub-message replies in the same order as they
where splitted. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>timeout</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <
b>Camel 2.5:</b> Sets a total timeout specified in millis. If the <a
shape="rect" href="recipient-list.html" title="Recipient List">Recipient
List</a> hasn't been able to split and process all replies within the given
timeframe, then the timeout triggers and the <a shape="rect"
href="splitter.html" title="Splitter">Splitter</a> breaks out and continues.
Notice if you provide a <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/processor/aggregate/TimeoutAwareAggregationStrategy.html";>TimeoutAwareAggregationStrategy</a>
then the <tt>timeout</tt> method is invoked before breaking out. If the
timeout is reached with running tasks still remaining, certain tasks for which
it is difficult for Camel to shut down in a graceful manner may continue to
run. So use this option with a bit of care. We may be able to improve this
functionality in future Camel releases. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd
"> <tt>onPrepareRef</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.8:</b> Refers to a custom <a shape="rect"
href="processor.html" title="Processor">Processor</a> to prepare the
sub-message of the <a shape="rect" href="exchange.html"
title="Exchange">Exchange</a>, before its processed. This allows you to do any
custom logic, such as deep-cloning the message payload if that's needed etc.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>shareUnitOfWork</tt> </td><td colspan="1" rowspan="1" class="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>
