Author: buildbot
Date: Wed Jul 18 09:20:01 2012
New Revision: 826184
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/aggregator2.html
websites/production/camel/content/bean.html
websites/production/camel/content/book-component-appendix.html
websites/production/camel/content/book-in-one-page.html
websites/production/camel/content/book-pattern-appendix.html
websites/production/camel/content/cache.html
websites/production/camel/content/cache/main.pageCache
Modified: websites/production/camel/content/aggregator2.html
==============================================================================
--- websites/production/camel/content/aggregator2.html (original)
+++ websites/production/camel/content/aggregator2.html Wed Jul 18 09:20:01 2012
@@ -199,13 +199,12 @@ If you need persistent repository then y
<h4><a shape="rect"
name="Aggregator2-UsingTimeoutAwareAggregationStrategy"></a>Using
TimeoutAwareAggregationStrategy</h4>
<p><b>Available as of Camel 2.9.2</b></p>
-<p>If your aggregation strategy implements
<tt>TimeoutAwareAggregationStrategy</tt>, then Camel will invoke the
<tt>timeout</tt> method when the timeout occurs. Notice that the values for
index, and total parameters will be -1, and the timeout parameter will only be
provided if configured as a fixed value. You must <b>not</b> throw any
exceptions from the <tt>timeout</tt> method.</p>
+<p>If your aggregation strategy implements
<tt>TimeoutAwareAggregationStrategy</tt>, then Camel will invoke the
<tt>timeout</tt> method when the timeout occurs. Notice that the values for
index and total parameters will be -1, and the timeout parameter will be
provided only if configured as a fixed value. You must <b>not</b> throw any
exceptions from the <tt>timeout</tt> method.</p>
<h4><a shape="rect"
name="Aggregator2-UsingCompletionAwareAggregationStrategy"></a>Using
CompletionAwareAggregationStrategy</h4>
<p><b>Available as of Camel 2.9.3</b></p>
-<p>If your aggregation strategy implements
<tt>CompletiomAwareAggregationStrategy</tt>, then Camel will invoke the
<tt>onComplete</tt> method when the aggregated Exchange is completed.<br
clear="none">
-This allows you to do any last minute custom logic, maybe to cleanup some
resources, or additional work on the exchange as its now completed.<br
clear="none">
+<p>If your aggregation strategy implements
<tt>CompletionAwareAggregationStrategy</tt>, then Camel will invoke the
<tt>onComplete</tt> method when the aggregated Exchange is completed. This
allows you to do any last minute custom logic such as to cleanup some
resources, or additional work on the exchange as it's now completed.<br
clear="none">
You must <b>not</b> throw any exceptions from the <tt>onCompletion</tt>
method.</p>
<h4><a shape="rect" name="Aggregator2-UsingcompletionSize"></a>Using
completionSize</h4>
Modified: websites/production/camel/content/bean.html
==============================================================================
--- websites/production/camel/content/bean.html (original)
+++ websites/production/camel/content/bean.html Wed Jul 18 09:20:01 2012
@@ -90,7 +90,7 @@ bean:beanID[?options]
<h3><a shape="rect" name="Bean-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"> Type </th><th colspan="1" rowspan="1"
class="confluenceTh"> Default </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>method</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>String</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> The method name from the bean that will be invoked. If
not provided, Camel will try to determine the method itself. In case of
ambiguity an exception will be thrown. See <a shape="rect"
href="bean-binding.html" title="Bean Binding">Bean Binding</a> for more
details. From <b>Camel 2.8</b> onwards you can specify type qualifiers to
pin-point exact method to use for overloaded methods. From <b>Camel 2.9</b>
onwards you can spe
cify parameter values directly in the method syntax. See more details at <a
shape="rect" href="bean-binding.html" title="Bean Binding">Bean Binding</a>.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>cache</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>boolean</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> If enabled, Camel will cache the
result of the first <a shape="rect" href="registry.html"
title="Registry">Registry</a> look-up. Cache can be enabled if the bean in the
<a shape="rect" href="registry.html" title="Registry">Registry</a> is defined
as a singleton scope. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>multiParameterArray</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>boolean</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <
b>Camel 1.5:</b> How to treat the parameters which are passed from the message
body; if it is <tt>true</tt>, the In message body should be an array of
parameters. </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"> Type </th><th colspan="1" rowspan="1"
class="confluenceTh"> Default </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>method</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>String</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> The method name from the bean that will be invoked. If
not provided, Camel will try to determine the method itself. In case of
ambiguity an exception will be thrown. See <a shape="rect"
href="bean-binding.html" title="Bean Binding">Bean Binding</a> for more
details. From <b>Camel 2.8</b> onwards you can specify type qualifiers to
pin-point the exact method to use for overloaded methods. From <b>Camel 2.9</b>
onwards you can
specify parameter values directly in the method syntax. See more details at
<a shape="rect" href="bean-binding.html" title="Bean Binding">Bean Binding</a>.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>cache</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>boolean</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> If enabled, Camel will cache the
result of the first <a shape="rect" href="registry.html"
title="Registry">Registry</a> look-up. Cache can be enabled if the bean in the
<a shape="rect" href="registry.html" title="Registry">Registry</a> is defined
as a singleton scope. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>multiParameterArray</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>boolean</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd
"> <b>Camel 1.5:</b> How to treat the parameters which are passed from the
message body; if it is <tt>true</tt>, the In message body should be an array of
parameters. </td></tr></tbody></table>
</div>
</div>
Modified: websites/production/camel/content/book-component-appendix.html
==============================================================================
--- websites/production/camel/content/book-component-appendix.html (original)
+++ websites/production/camel/content/book-component-appendix.html Wed Jul 18
09:20:01 2012
@@ -691,7 +691,7 @@ bean:beanID[?options]
<h3><a shape="rect" name="BookComponentAppendix-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"> Type </th><th colspan="1" rowspan="1"
class="confluenceTh"> Default </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>method</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>String</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> The method name from the bean that will be invoked. If
not provided, Camel will try to determine the method itself. In case of
ambiguity an exception will be thrown. See <a shape="rect"
href="bean-binding.html" title="Bean Binding">Bean Binding</a> for more
details. From <b>Camel 2.8</b> onwards you can specify type qualifiers to
pin-point exact method to use for overloaded methods. From <b>Camel 2.9</b>
onwards you can spe
cify parameter values directly in the method syntax. See more details at <a
shape="rect" href="bean-binding.html" title="Bean Binding">Bean Binding</a>.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>cache</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>boolean</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> If enabled, Camel will cache the
result of the first <a shape="rect" href="registry.html"
title="Registry">Registry</a> look-up. Cache can be enabled if the bean in the
<a shape="rect" href="registry.html" title="Registry">Registry</a> is defined
as a singleton scope. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>multiParameterArray</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>boolean</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <
b>Camel 1.5:</b> How to treat the parameters which are passed from the message
body; if it is <tt>true</tt>, the In message body should be an array of
parameters. </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"> Type </th><th colspan="1" rowspan="1"
class="confluenceTh"> Default </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>method</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>String</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> The method name from the bean that will be invoked. If
not provided, Camel will try to determine the method itself. In case of
ambiguity an exception will be thrown. See <a shape="rect"
href="bean-binding.html" title="Bean Binding">Bean Binding</a> for more
details. From <b>Camel 2.8</b> onwards you can specify type qualifiers to
pin-point the exact method to use for overloaded methods. From <b>Camel 2.9</b>
onwards you can
specify parameter values directly in the method syntax. See more details at
<a shape="rect" href="bean-binding.html" title="Bean Binding">Bean Binding</a>.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>cache</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>boolean</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> If enabled, Camel will cache the
result of the first <a shape="rect" href="registry.html"
title="Registry">Registry</a> look-up. Cache can be enabled if the bean in the
<a shape="rect" href="registry.html" title="Registry">Registry</a> is defined
as a singleton scope. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>multiParameterArray</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>boolean</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd
"> <b>Camel 1.5:</b> How to treat the parameters which are passed from the
message body; if it is <tt>true</tt>, the In message body should be an array of
parameters. </td></tr></tbody></table>
</div>
</div>
@@ -1110,7 +1110,7 @@ cache:<span class="code-comment">//cache
</div>
</div>
-<p>The <tt>CamelCacheAdd</tt> and <tt>CamelCacheUpdate</tt> supports
additional headers to control time to live, time to idle, and eternal. </p>
+<p>The <tt>CamelCacheAdd</tt> and <tt>CamelCacheUpdate</tt> operations support
additional headers: </p>
<div class="confluenceTableSmall"><div class="table-wrap">
<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Header </th><th colspan="1" rowspan="1"
class="confluenceTh"> Type </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>CamelCacheTimeToLive</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>Integer</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <b>Camel 2.11:</b> Time to live in seconds.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>CamelCacheTimeToIdle</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>Integer</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.11:</b> Time to idle in seconds.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>CamelCacheEternal</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>Boolean</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.11:
</b> Whether the content is eternal. </td></tr></tbody></table>
</div>
Modified: websites/production/camel/content/book-in-one-page.html
==============================================================================
--- websites/production/camel/content/book-in-one-page.html (original)
+++ websites/production/camel/content/book-in-one-page.html Wed Jul 18 09:20:01
2012
@@ -16598,13 +16598,12 @@ If you need persistent repository then y
<h4><a shape="rect"
name="BookInOnePage-UsingTimeoutAwareAggregationStrategy"></a>Using
TimeoutAwareAggregationStrategy</h4>
<p><b>Available as of Camel 2.9.2</b></p>
-<p>If your aggregation strategy implements
<tt>TimeoutAwareAggregationStrategy</tt>, then Camel will invoke the
<tt>timeout</tt> method when the timeout occurs. Notice that the values for
index, and total parameters will be -1, and the timeout parameter will only be
provided if configured as a fixed value. You must <b>not</b> throw any
exceptions from the <tt>timeout</tt> method.</p>
+<p>If your aggregation strategy implements
<tt>TimeoutAwareAggregationStrategy</tt>, then Camel will invoke the
<tt>timeout</tt> method when the timeout occurs. Notice that the values for
index and total parameters will be -1, and the timeout parameter will be
provided only if configured as a fixed value. You must <b>not</b> throw any
exceptions from the <tt>timeout</tt> method.</p>
<h4><a shape="rect"
name="BookInOnePage-UsingCompletionAwareAggregationStrategy"></a>Using
CompletionAwareAggregationStrategy</h4>
<p><b>Available as of Camel 2.9.3</b></p>
-<p>If your aggregation strategy implements
<tt>CompletiomAwareAggregationStrategy</tt>, then Camel will invoke the
<tt>onComplete</tt> method when the aggregated Exchange is completed.<br
clear="none">
-This allows you to do any last minute custom logic, maybe to cleanup some
resources, or additional work on the exchange as its now completed.<br
clear="none">
+<p>If your aggregation strategy implements
<tt>CompletionAwareAggregationStrategy</tt>, then Camel will invoke the
<tt>onComplete</tt> method when the aggregated Exchange is completed. This
allows you to do any last minute custom logic such as to cleanup some
resources, or additional work on the exchange as it's now completed.<br
clear="none">
You must <b>not</b> throw any exceptions from the <tt>onCompletion</tt>
method.</p>
<h4><a shape="rect" name="BookInOnePage-UsingcompletionSize"></a>Using
completionSize</h4>
@@ -21199,7 +21198,7 @@ bean:beanID[?options]
<h3><a shape="rect" name="BookInOnePage-Options"></a>Options</h3>
<div class="confluenceTableSmall"><div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Name </th><th colspan="1" rowspan="1"
class="confluenceTh"> Type </th><th colspan="1" rowspan="1"
class="confluenceTh"> Default </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>method</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>String</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> The method name from the bean that will be invoked. If
not provided, Camel will try to determine the method itself. In case of
ambiguity an exception will be thrown. See <a shape="rect"
href="bean-binding.html" title="Bean Binding">Bean Binding</a> for more
details. From <b>Camel 2.8</b> onwards you can specify type qualifiers to
pin-point exact method to use for overloaded methods. From <b>Camel 2.9</b>
onwards you can spe
cify parameter values directly in the method syntax. See more details at <a
shape="rect" href="bean-binding.html" title="Bean Binding">Bean Binding</a>.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>cache</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>boolean</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> If enabled, Camel will cache the
result of the first <a shape="rect" href="registry.html"
title="Registry">Registry</a> look-up. Cache can be enabled if the bean in the
<a shape="rect" href="registry.html" title="Registry">Registry</a> is defined
as a singleton scope. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>multiParameterArray</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>boolean</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <
b>Camel 1.5:</b> How to treat the parameters which are passed from the message
body; if it is <tt>true</tt>, the In message body should be an array of
parameters. </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"> Type </th><th colspan="1" rowspan="1"
class="confluenceTh"> Default </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>method</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>String</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> The method name from the bean that will be invoked. If
not provided, Camel will try to determine the method itself. In case of
ambiguity an exception will be thrown. See <a shape="rect"
href="bean-binding.html" title="Bean Binding">Bean Binding</a> for more
details. From <b>Camel 2.8</b> onwards you can specify type qualifiers to
pin-point the exact method to use for overloaded methods. From <b>Camel 2.9</b>
onwards you can
specify parameter values directly in the method syntax. See more details at
<a shape="rect" href="bean-binding.html" title="Bean Binding">Bean Binding</a>.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>cache</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>boolean</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> If enabled, Camel will cache the
result of the first <a shape="rect" href="registry.html"
title="Registry">Registry</a> look-up. Cache can be enabled if the bean in the
<a shape="rect" href="registry.html" title="Registry">Registry</a> is defined
as a singleton scope. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>multiParameterArray</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>boolean</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd
"> <b>Camel 1.5:</b> How to treat the parameters which are passed from the
message body; if it is <tt>true</tt>, the In message body should be an array of
parameters. </td></tr></tbody></table>
</div>
</div>
@@ -21618,7 +21617,7 @@ cache:<span class="code-comment">//cache
</div>
</div>
-<p>The <tt>CamelCacheAdd</tt> and <tt>CamelCacheUpdate</tt> supports
additional headers to control time to live, time to idle, and eternal. </p>
+<p>The <tt>CamelCacheAdd</tt> and <tt>CamelCacheUpdate</tt> operations support
additional headers: </p>
<div class="confluenceTableSmall"><div class="table-wrap">
<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Header </th><th colspan="1" rowspan="1"
class="confluenceTh"> Type </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>CamelCacheTimeToLive</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>Integer</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <b>Camel 2.11:</b> Time to live in seconds.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>CamelCacheTimeToIdle</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>Integer</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.11:</b> Time to idle in seconds.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>CamelCacheEternal</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>Boolean</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.11:
</b> Whether the content is eternal. </td></tr></tbody></table>
</div>
Modified: websites/production/camel/content/book-pattern-appendix.html
==============================================================================
--- websites/production/camel/content/book-pattern-appendix.html (original)
+++ websites/production/camel/content/book-pattern-appendix.html Wed Jul 18
09:20:01 2012
@@ -2334,13 +2334,12 @@ If you need persistent repository then y
<h4><a shape="rect"
name="BookPatternAppendix-UsingTimeoutAwareAggregationStrategy"></a>Using
TimeoutAwareAggregationStrategy</h4>
<p><b>Available as of Camel 2.9.2</b></p>
-<p>If your aggregation strategy implements
<tt>TimeoutAwareAggregationStrategy</tt>, then Camel will invoke the
<tt>timeout</tt> method when the timeout occurs. Notice that the values for
index, and total parameters will be -1, and the timeout parameter will only be
provided if configured as a fixed value. You must <b>not</b> throw any
exceptions from the <tt>timeout</tt> method.</p>
+<p>If your aggregation strategy implements
<tt>TimeoutAwareAggregationStrategy</tt>, then Camel will invoke the
<tt>timeout</tt> method when the timeout occurs. Notice that the values for
index and total parameters will be -1, and the timeout parameter will be
provided only if configured as a fixed value. You must <b>not</b> throw any
exceptions from the <tt>timeout</tt> method.</p>
<h4><a shape="rect"
name="BookPatternAppendix-UsingCompletionAwareAggregationStrategy"></a>Using
CompletionAwareAggregationStrategy</h4>
<p><b>Available as of Camel 2.9.3</b></p>
-<p>If your aggregation strategy implements
<tt>CompletiomAwareAggregationStrategy</tt>, then Camel will invoke the
<tt>onComplete</tt> method when the aggregated Exchange is completed.<br
clear="none">
-This allows you to do any last minute custom logic, maybe to cleanup some
resources, or additional work on the exchange as its now completed.<br
clear="none">
+<p>If your aggregation strategy implements
<tt>CompletionAwareAggregationStrategy</tt>, then Camel will invoke the
<tt>onComplete</tt> method when the aggregated Exchange is completed. This
allows you to do any last minute custom logic such as to cleanup some
resources, or additional work on the exchange as it's now completed.<br
clear="none">
You must <b>not</b> throw any exceptions from the <tt>onCompletion</tt>
method.</p>
<h4><a shape="rect" name="BookPatternAppendix-UsingcompletionSize"></a>Using
completionSize</h4>
Modified: websites/production/camel/content/cache.html
==============================================================================
--- websites/production/camel/content/cache.html (original)
+++ websites/production/camel/content/cache.html Wed Jul 18 09:20:01 2012
@@ -139,7 +139,7 @@ cache:<span class="code-comment">//cache
</div>
</div>
-<p>The <tt>CamelCacheAdd</tt> and <tt>CamelCacheUpdate</tt> supports
additional headers to control time to live, time to idle, and eternal. </p>
+<p>The <tt>CamelCacheAdd</tt> and <tt>CamelCacheUpdate</tt> operations support
additional headers: </p>
<div class="confluenceTableSmall"><div class="table-wrap">
<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Header </th><th colspan="1" rowspan="1"
class="confluenceTh"> Type </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>CamelCacheTimeToLive</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>Integer</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <b>Camel 2.11:</b> Time to live in seconds.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>CamelCacheTimeToIdle</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>Integer</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.11:</b> Time to idle in seconds.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>CamelCacheEternal</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>Boolean</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.11:
</b> Whether the content is eternal. </td></tr></tbody></table>
</div>
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
