camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r839534 - in /websites/production/camel/content: book-component-appendix.html book-in-one-page.html cache/main.pageCache camel-2110-release.html seda.html
Date Sun, 25 Nov 2012 15:23:34 GMT
Author: buildbot
Date: Sun Nov 25 15:23:33 2012
New Revision: 839534

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/book-component-appendix.html
    websites/production/camel/content/book-in-one-page.html
    websites/production/camel/content/cache/main.pageCache
    websites/production/camel/content/camel-2110-release.html
    websites/production/camel/content/seda.html

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 Sun Nov 25 15:23:33 2012
@@ -14360,7 +14360,7 @@ seda:someName[?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"> Since </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>size</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> The maximum capacity of the SEDA queue (i.e., the number of messages it can hold). The default value in Camel 2.2 or older is <tt>1000</tt>. From Camel 2.3 onwards, the size is unbounded by default. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>concurrentConsumers</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>1</tt> </td><td colspan="1" rowspan="
 1" class="confluenceTd"> Number of concurrent threads processing exchanges. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>waitForTaskToComplete</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>IfReplyExpected</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Option to specify whether the caller should wait for the async task to complete or not before continuing. The following three options are supported: <tt>Always</tt>, <tt>Never</tt> or <tt>IfReplyExpected</tt>. The first two values are self-explanatory. The last value, <tt>IfReplyExpected</tt>, will only wait if the message is <a shape="rect" href="request-reply.html" title="Request Reply">Request Reply</a> based. The default option is <tt>IfReplyExpected</tt>. See more information about <a shape="rect" href="async.html" title="Async">Async</a> messaging. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"
 > <tt>timeout</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>30000</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Timeout (in milliseconds) before a SEDA producer will stop waiting for an asynchronous task to complete. See <tt>waitForTaskToComplete</tt> and <a shape="rect" href="async.html" title="Async">Async</a> for more details. In <b>Camel 2.2</b> you can now disable timeout by using 0 or a negative value. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>multipleConsumers</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>2.2</b> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies whether multiple consumers are allowed. If enabled, you can use <a shape="rect" href="seda.html" title="SEDA">SEDA</a> for <a shape="rect" class="external-link" href="http://en.wikipedia.org/wi
 ki/Publish%E2%80%93subscribe_pattern" rel="nofollow">Publish-Subscribe</a> messaging. That is, you can send a message to the SEDA queue and have each consumer receive a copy of the message. When enabled, this option should be specified on every consumer endpoint. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>limitConcurrentConsumers</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>2.3</b> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>true</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Whether to limit the number of <tt>concurrentConsumers</tt> to the maximum of <tt>500</tt>. By default, an exception will be thrown if a SEDA endpoint is configured with a greater number. You can disable that check by turning this option off. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>blockWhenFull</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>2.9</b> </td><td colspan="1" rowspan="1" class="c
 onfluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Whether a thread that sends messages to a full SEDA queue will block until the queue's capacity is no longer exhausted.  By default, an exception will be thrown stating that the queue is full. By enabling this option, the calling thread will instead block and wait until the message can be accepted. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>queueSize</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>2.9</b> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Component only:</b> The maximum default size (capacity of the number of messages it can hold) of the SEDA queue. This option is used if <tt>size</tt> is not in use. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>pollTimeout</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>2.9.3</b> </td><td colspan="1"
  rowspan="1" class="confluenceTd"> <tt>1000</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <em>Consumer only</em> &#8211; The timeout used when polling. When a timeout occurs, the consumer can check whether it is allowed to continue running. Setting a lower value allows the consumer to react more quickly upon shutdown. </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"> Since </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>size</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> The maximum capacity of the SEDA queue (i.e., the number of messages it can hold). The default value in Camel 2.2 or older is <tt>1000</tt>. From Camel 2.3 onwards, the size is unbounded by default. <b>Notice:</b> Mind if you use this option, then its the first endpoint being created with the queue name, that determines the size. To make sure all endpoints use same size, then configure the size option on all of them, or the first endpoint being
  created. From <b>Camel 2.11</b> onwards, a validation is taken place to ensure if using mixed queue sizes for the same queue name, Camel would detect this and fail creating the endpoint. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>concurrentConsumers</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>1</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Number of concurrent threads processing exchanges. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>waitForTaskToComplete</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>IfReplyExpected</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Option to specify whether the caller should wait for the async task to complete or not before continuing. The following three options are supported: <tt>Always</tt>, <tt>Never</tt> or <t
 t>IfReplyExpected</tt>. The first two values are self-explanatory. The last value, <tt>IfReplyExpected</tt>, will only wait if the message is <a shape="rect" href="request-reply.html" title="Request Reply">Request Reply</a> based. The default option is <tt>IfReplyExpected</tt>. See more information about <a shape="rect" href="async.html" title="Async">Async</a> messaging. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>timeout</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>30000</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Timeout (in milliseconds) before a SEDA producer will stop waiting for an asynchronous task to complete. See <tt>waitForTaskToComplete</tt> and <a shape="rect" href="async.html" title="Async">Async</a> for more details. In <b>Camel 2.2</b> you can now disable timeout by using 0 or a negative value. </td></tr><tr><td colspan="1" rowspan="1" class=
 "confluenceTd"> <tt>multipleConsumers</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>2.2</b> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies whether multiple consumers are allowed. If enabled, you can use <a shape="rect" href="seda.html" title="SEDA">SEDA</a> for <a shape="rect" class="external-link" href="http://en.wikipedia.org/wiki/Publish%E2%80%93subscribe_pattern" rel="nofollow">Publish-Subscribe</a> messaging. That is, you can send a message to the SEDA queue and have each consumer receive a copy of the message. When enabled, this option should be specified on every consumer endpoint. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>limitConcurrentConsumers</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>2.3</b> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>true</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> 
 Whether to limit the number of <tt>concurrentConsumers</tt> to the maximum of <tt>500</tt>. By default, an exception will be thrown if a SEDA endpoint is configured with a greater number. You can disable that check by turning this option off. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>blockWhenFull</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>2.9</b> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Whether a thread that sends messages to a full SEDA queue will block until the queue's capacity is no longer exhausted.  By default, an exception will be thrown stating that the queue is full. By enabling this option, the calling thread will instead block and wait until the message can be accepted. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>queueSize</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>2.9</b> </td><td colspan="1
 " rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Component only:</b> The maximum default size (capacity of the number of messages it can hold) of the SEDA queue. This option is used if <tt>size</tt> is not in use. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>pollTimeout</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>2.9.3</b> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>1000</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <em>Consumer only</em> &#8211; The timeout used when polling. When a timeout occurs, the consumer can check whether it is allowed to continue running. Setting a lower value allows the consumer to react more quickly upon shutdown. </td></tr></tbody></table>
 </div>
 </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 Sun Nov 25 15:23:33 2012
@@ -34596,7 +34596,7 @@ seda:someName[?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"> Since </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>size</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> The maximum capacity of the SEDA queue (i.e., the number of messages it can hold). The default value in Camel 2.2 or older is <tt>1000</tt>. From Camel 2.3 onwards, the size is unbounded by default. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>concurrentConsumers</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>1</tt> </td><td colspan="1" rowspan="
 1" class="confluenceTd"> Number of concurrent threads processing exchanges. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>waitForTaskToComplete</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>IfReplyExpected</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Option to specify whether the caller should wait for the async task to complete or not before continuing. The following three options are supported: <tt>Always</tt>, <tt>Never</tt> or <tt>IfReplyExpected</tt>. The first two values are self-explanatory. The last value, <tt>IfReplyExpected</tt>, will only wait if the message is <a shape="rect" href="request-reply.html" title="Request Reply">Request Reply</a> based. The default option is <tt>IfReplyExpected</tt>. See more information about <a shape="rect" href="async.html" title="Async">Async</a> messaging. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"
 > <tt>timeout</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>30000</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Timeout (in milliseconds) before a SEDA producer will stop waiting for an asynchronous task to complete. See <tt>waitForTaskToComplete</tt> and <a shape="rect" href="async.html" title="Async">Async</a> for more details. In <b>Camel 2.2</b> you can now disable timeout by using 0 or a negative value. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>multipleConsumers</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>2.2</b> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies whether multiple consumers are allowed. If enabled, you can use <a shape="rect" href="seda.html" title="SEDA">SEDA</a> for <a shape="rect" class="external-link" href="http://en.wikipedia.org/wi
 ki/Publish%E2%80%93subscribe_pattern" rel="nofollow">Publish-Subscribe</a> messaging. That is, you can send a message to the SEDA queue and have each consumer receive a copy of the message. When enabled, this option should be specified on every consumer endpoint. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>limitConcurrentConsumers</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>2.3</b> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>true</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Whether to limit the number of <tt>concurrentConsumers</tt> to the maximum of <tt>500</tt>. By default, an exception will be thrown if a SEDA endpoint is configured with a greater number. You can disable that check by turning this option off. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>blockWhenFull</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>2.9</b> </td><td colspan="1" rowspan="1" class="c
 onfluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Whether a thread that sends messages to a full SEDA queue will block until the queue's capacity is no longer exhausted.  By default, an exception will be thrown stating that the queue is full. By enabling this option, the calling thread will instead block and wait until the message can be accepted. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>queueSize</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>2.9</b> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Component only:</b> The maximum default size (capacity of the number of messages it can hold) of the SEDA queue. This option is used if <tt>size</tt> is not in use. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>pollTimeout</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>2.9.3</b> </td><td colspan="1"
  rowspan="1" class="confluenceTd"> <tt>1000</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <em>Consumer only</em> &#8211; The timeout used when polling. When a timeout occurs, the consumer can check whether it is allowed to continue running. Setting a lower value allows the consumer to react more quickly upon shutdown. </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"> Since </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>size</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> The maximum capacity of the SEDA queue (i.e., the number of messages it can hold). The default value in Camel 2.2 or older is <tt>1000</tt>. From Camel 2.3 onwards, the size is unbounded by default. <b>Notice:</b> Mind if you use this option, then its the first endpoint being created with the queue name, that determines the size. To make sure all endpoints use same size, then configure the size option on all of them, or the first endpoint being
  created. From <b>Camel 2.11</b> onwards, a validation is taken place to ensure if using mixed queue sizes for the same queue name, Camel would detect this and fail creating the endpoint. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>concurrentConsumers</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>1</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Number of concurrent threads processing exchanges. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>waitForTaskToComplete</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>IfReplyExpected</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Option to specify whether the caller should wait for the async task to complete or not before continuing. The following three options are supported: <tt>Always</tt>, <tt>Never</tt> or <t
 t>IfReplyExpected</tt>. The first two values are self-explanatory. The last value, <tt>IfReplyExpected</tt>, will only wait if the message is <a shape="rect" href="request-reply.html" title="Request Reply">Request Reply</a> based. The default option is <tt>IfReplyExpected</tt>. See more information about <a shape="rect" href="async.html" title="Async">Async</a> messaging. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>timeout</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>30000</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Timeout (in milliseconds) before a SEDA producer will stop waiting for an asynchronous task to complete. See <tt>waitForTaskToComplete</tt> and <a shape="rect" href="async.html" title="Async">Async</a> for more details. In <b>Camel 2.2</b> you can now disable timeout by using 0 or a negative value. </td></tr><tr><td colspan="1" rowspan="1" class=
 "confluenceTd"> <tt>multipleConsumers</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>2.2</b> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies whether multiple consumers are allowed. If enabled, you can use <a shape="rect" href="seda.html" title="SEDA">SEDA</a> for <a shape="rect" class="external-link" href="http://en.wikipedia.org/wiki/Publish%E2%80%93subscribe_pattern" rel="nofollow">Publish-Subscribe</a> messaging. That is, you can send a message to the SEDA queue and have each consumer receive a copy of the message. When enabled, this option should be specified on every consumer endpoint. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>limitConcurrentConsumers</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>2.3</b> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>true</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> 
 Whether to limit the number of <tt>concurrentConsumers</tt> to the maximum of <tt>500</tt>. By default, an exception will be thrown if a SEDA endpoint is configured with a greater number. You can disable that check by turning this option off. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>blockWhenFull</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>2.9</b> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Whether a thread that sends messages to a full SEDA queue will block until the queue's capacity is no longer exhausted.  By default, an exception will be thrown stating that the queue is full. By enabling this option, the calling thread will instead block and wait until the message can be accepted. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>queueSize</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>2.9</b> </td><td colspan="1
 " rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Component only:</b> The maximum default size (capacity of the number of messages it can hold) of the SEDA queue. This option is used if <tt>size</tt> is not in use. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>pollTimeout</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>2.9.3</b> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>1000</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <em>Consumer only</em> &#8211; The timeout used when polling. When a timeout occurs, the consumer can check whether it is allowed to continue running. Setting a lower value allows the consumer to react more quickly upon shutdown. </td></tr></tbody></table>
 </div>
 </div>
 

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

Modified: websites/production/camel/content/camel-2110-release.html
==============================================================================
--- websites/production/camel/content/camel-2110-release.html (original)
+++ websites/production/camel/content/camel-2110-release.html Sun Nov 25 15:23:33 2012
@@ -84,7 +84,7 @@
 
 <p>Welcome to the 2.11.0 release with approximately XXX issues resolved - including new features, improvements, and bug fixes, such as: </p>
 
-<ul><li>Added <a shape="rect" href="binding.html" title="Binding">Binding</a> support, so it is easy to combine things like a <a shape="rect" href="data-format.html" title="Data Format">Data Format</a> to an <a shape="rect" href="endpoint.html" title="Endpoint">Endpoint</a> for easier composition of routes.</li><li>Added support for SOAP 1.2 in <a shape="rect" href="soap.html" title="SOAP">SOAP</a> data format.</li><li><a shape="rect" href="cache.html" title="Cache">Cache</a> operation for add/update now supports expiry headers to control time to live/idle/eternal.</li><li>Added <tt>allowNullBody</tt> option to <a shape="rect" href="jms.html" title="JMS">JMS</a> to configure whether sending messages with no body is allowed.</li><li>Added <tt>connectOnStartup</tt> option to <a shape="rect" href="hdfs.html" title="HDFS">HDFS</a> to allow to connect on demand, to avoid having Hadoop block for long time connecting to the HDFS cluster, as it has a hardcoded 15 minute retry mechan
 ism.</li><li>Added support for daily and weekly trends to <a shape="rect" href="twitter.html" title="Twitter">Twitter</a> component.</li><li>The <a shape="rect" href="camel-maven-archetypes.html" title="Camel Maven Archetypes">Camel Maven Archetypes</a> now generates projects without any license headers.</li><li>Added 'rejectOld' option to the <a shape="rect" href="resequencer.html" title="Resequencer">Resequencer</a> to prevent out of order messages from being delivered after capacity/timeout events occur</li><li>Further optimized <a shape="rect" href="xpath.html" title="XPath">XPath</a> under concurrent load, and as well ensured resources are cleaned up eagerly</li><li>Added options <tt>allowNullBody</tt> and <tt>readLockMinLength</tt> to the <a shape="rect" href="file2.html" title="File2">File</a> and <a shape="rect" href="ftp2.html" title="FTP2">FTP</a> components.</li><li>Made <tt>changed</tt> read lock strategy on <a shape="rect" href="ftp2.html" title="FTP2">FTP</a> g
 o faster (eg when the FTP server has a lot of files in the directory) if you enable the <tt>fastExistsCheck=true</tt> option as well. Notice that some FTP server may not support this.</li><li><a shape="rect" href="hl7.html" title="HL7">HL7</a> moves to HAPI 2.0 and supports using a dedicated Parser instance in the <a shape="rect" href="hl7.html" title="HL7">HL7</a> MLLP codec and DataFormat. Added "Terser" language and expression to be able to extract fields from a parsed message. <a shape="rect" href="hl7.html" title="HL7">HL7</a> now uses Apache Mina 2.x.</li><li>Add an option <tt>HttpMethodRestrict</tt> to restrict HTTP method in <a shape="rect" href="jetty.html" title="Jetty">Jetty</a> and <a shape="rect" href="servlet.html" title="SERVLET">SERVLET</a></li><li>Add support for selection of <a shape="rect" href="direct-vm.html" title="Direct-VM">Direct-VM</a> consumers by using ant-like path expression.</li><li>The <a shape="rect" href="pojo-producing.html" title="POJO Pro
 ducing">POJO Producing</a>, and <a shape="rect" href="pojo-consuming.html" title="POJO Consuming">POJO Consuming</a> with @Consume, @Produce, @EndpointInject now supports a new {{property} attribute to get the endpoint configuration from a bean property (eg using a getter method); this allows you to configure this on the bean using conventional bean configuration.</li><li>Testing with <tt>camel-test-blueprint</tt> on Windows no longer tries to cleanup after testing taking up 5 seconds and logging WARNs.</li><li>The <a shape="rect" href="file2.html" title="File2">File</a>, and <a shape="rect" href="ftp2.html" title="FTP2">FTP</a> components now support <tt>fileExist=Move</tt> option to move any existing files before writing a file.</li><li>Added option <tt>loadStatisticsEnabled</tt> on <a shape="rect" href="camel-jmx.html" title="Camel JMX">Camel JMX</a> to allow to disable load statistics if not needed (avoids a background thread being in use, to calculate the load stats).</
 li><li>Enabled "lazy connections" for <a shape="rect" href="xmpp.html" title="XMPP">XMPP</a> providers via the <tt>testConnectionOnStartup</tt> option</li><li>Added a connection monitor to detect and fix dropped <a shape="rect" href="xmpp.html" title="XMPP">XMPP</a> consumer connections at configurable <tt>connectionPollDelay</tt> intervals</li><li>Added an <tt>org.apache.camel.builder.ExchangeBuilder</tt> to build the <a shape="rect" href="exchange.html" title="Exchange">Exchange</a> using a builder pattern.</li><li>The <a shape="rect" href="camel-run-maven-goal.html" title="Camel Run Maven Goal">Camel Run Maven Goal</a> can now run <a shape="rect" href="cdi.html" title="CDI">CDI</a> applications.</li><li>The Camel <a shape="rect" href="cdi.html" title="CDI">CDI</a> component has improved a lot.</li><li>Added option <tt>allowRedeliveryWhileStopping</tt> to <a shape="rect" href="dead-letter-channel.html" title="Dead Letter Channel">error handlers</a> to control if redelivery
  is allowed during stopping/shutting down Camel or the route(s). Turning this option <tt>false</tt> allows to stop quicker by rejecting redelivery attempts.</li><li>Added support for specifying user info in Camel <a shape="rect" href="endpoint.html" title="Endpoint">Endpoint</a> urls, which contains the @ sign; now the @ sign can be given as is; without being encoded to %40.</li><li>Added robust connection support for <a shape="rect" href="jmx.html" title="JMX">JMX</a>. Optional <tt>testConnectionOnStartup</tt> allows a JMX consumer to attach to a JMX server that becomes available <em>after</em> the JMX endpoint starts; <tt>reconnectOnConnectionFailure</tt> enables re-connection of failed JMX connections.</li><li><a shape="rect" href="jaxb.html" title="JAXB">JAXB</a> and <a shape="rect" href="soap.html" title="SOAP">SOAP</a> data format now supports controlling namespace prefix mappings when marshalling (eg to avoid prefixes such as ns2, ns3, ns4 etc.)</li><li>Added support 
 for using raw uris when <a shape="rect" href="component.html" title="Component">Component</a>s create <a shape="rect" href="endpoint.html" title="Endpoint">Endpoint</a>s. This gives component writers full power in case their component has special syntax/notation for endpoint uri configurations.</li><li><a shape="rect" href="eip.html" title="EIP">EIP</a>s configured with custom <tt>AggregationStrategy</tt> will now strict check the custom strategy exists in the <a shape="rect" href="registry.html" title="Registry">Registry</a> and no longer fallback and use a default strategy if not.</li><li>Camel now logs on shutdown if any thread pools hasn't been properly shutdown, and will shutdown them as fail safe (can only be done for the thread pools Camel manages).</li><li>The buffer size of <a shape="rect" href="stream-caching.html" title="Stream caching">Stream caching</a> is now configurable.</li><li>Improved startup performance.</li><li>Added <a shape="rect" href="jms.html" title
 ="JMS">JMS</a> URI option <tt>messageListenerContainerFactoryRef</tt> which allows you to specify a <tt>MessageListenerContainerFactory</tt> to determine what <tt>org.springframework.jms.listener.AbstractMessageListenerContainer</tt> to use to consume messages.</li><li><a shape="rect" href="mqtt.html" title="MQTT">MQTT</a> producer now leverages the <a shape="rect" href="asynchronous-routing-engine.html" title="Asynchronous Routing Engine">Asynchronous Routing Engine</a></li><li>The <a shape="rect" href="netty.html" title="Netty">Netty</a> producer scales up and down much better by leveraging a channel pool.</li><li>Added new <a shape="rect" href="camel-maven-archetypes.html" title="Camel Maven Archetypes">Camel Maven Archetypes</a> for creating Camel and Groovy applications.</li><li>Camel now injects <tt>CamelContext</tt> on <tt>Language</tt> and <tt>DataFormat</tt> that implements <tt>CamelContextAware</tt></li><li>Thread pools in Camel with <tt>maximumQueueSize</tt> of 0 
 or negative will now not use a worker queue but do direct hand-over to thread instead.</li><li><a shape="rect" href="simple.html" title="Simple">Simple</a> unary operators for inc and dec must now have function on left hand side, to be parsed as unary function. Otherwise its now regarded as literal.</li><li>Custom assigned id's on Camel <a shape="rect" href="routes.html" title="Routes">Routes</a> is now validated on starting the routes, that they must be unique within the same CamelContext.</li><li>Added <tt>AbstractListAggregationStrategy</tt> abstract class to make it easier to <a shape="rect" href="aggregator2.html" title="Aggregator2">aggregate</a> into a List&lt;V&gt; using a custom <tt>AggregationStrategy</tt>.</li><li><a shape="rect" href="eip.html" title="EIP">EIP</a>s which support using <tt>AggregationStrategy</tt> now control the lifecycle of the strategy; allowing end users to do custom logic in the start/stop methods of their strategy implementation.</li><li>Add
 ed option <tt>includeSentJMSMessageID</tt> to <a shape="rect" href="jms.html" title="JMS">JMS</a> to allow to enrich Camel Message with the actual JMSMessageID for the sent message. Can be used by end users for logging purpose etc.</li><li>Added option <tt>allowShortLines</tt> and <tt>ignoreExtraColumns</tt> to <a shape="rect" href="flatpack-dataformat.html" title="Flatpack DataFormat">Flatpack data format</a>.</li><li><a shape="rect" href="mail.html" title="Mail">Mail</a> consumer now supports using search terms to filter mails by terms such as subject, from, body, sent date etc.</li><li>The cached script file in the <a shape="rect" href="language.html" title="Language">Language</a> component can now be cleared via JMX.</li><li>improved the karaf context-info command by adding a verbose mode to view endpoints list (now hidden by default) and adding stats on the number of active/inactive routes</li><li>Added support for <tt>UpdateList</tt>, <tt>DeleteList</tt> and <tt>Execut
 orType</tt> to <a shape="rect" href="mybatis.html" title="MyBatis">MyBatis</a> component.</li><li>Added support for easier configuration of using concurrent message listener consumer when doing request/reply over <a shape="rect" href="jms.html" title="JMS">JMS</a>, by leveraging the existing <tt>concurrentConsumers</tt> and <tt>maxConcurrentConsumers</tt> options.</li><li>Improved the <a shape="rect" href="smpp.html" title="SMPP">SMPP</a> consumer to expose more data by receiving a <tt>DeliverSM</tt> message.</li><li>Camels <a shape="rect" href="using-propertyplaceholder.html" title="Using PropertyPlaceholder">property placeholders</a> can now be used in route id / node id's in the routes in XML and Java DSLs, eg &lt;route id="<tt>coolName</tt>"&gt;</li><li>The thread name pattern can easily be configured on &lt;camelContext&gt; with the new threadNamePattern attribute</li></ul>
+<ul><li>Added <a shape="rect" href="binding.html" title="Binding">Binding</a> support, so it is easy to combine things like a <a shape="rect" href="data-format.html" title="Data Format">Data Format</a> to an <a shape="rect" href="endpoint.html" title="Endpoint">Endpoint</a> for easier composition of routes.</li><li>Added support for SOAP 1.2 in <a shape="rect" href="soap.html" title="SOAP">SOAP</a> data format.</li><li><a shape="rect" href="cache.html" title="Cache">Cache</a> operation for add/update now supports expiry headers to control time to live/idle/eternal.</li><li>Added <tt>allowNullBody</tt> option to <a shape="rect" href="jms.html" title="JMS">JMS</a> to configure whether sending messages with no body is allowed.</li><li>Added <tt>connectOnStartup</tt> option to <a shape="rect" href="hdfs.html" title="HDFS">HDFS</a> to allow to connect on demand, to avoid having Hadoop block for long time connecting to the HDFS cluster, as it has a hardcoded 15 minute retry mechan
 ism.</li><li>Added support for daily and weekly trends to <a shape="rect" href="twitter.html" title="Twitter">Twitter</a> component.</li><li>The <a shape="rect" href="camel-maven-archetypes.html" title="Camel Maven Archetypes">Camel Maven Archetypes</a> now generates projects without any license headers.</li><li>Added 'rejectOld' option to the <a shape="rect" href="resequencer.html" title="Resequencer">Resequencer</a> to prevent out of order messages from being delivered after capacity/timeout events occur</li><li>Further optimized <a shape="rect" href="xpath.html" title="XPath">XPath</a> under concurrent load, and as well ensured resources are cleaned up eagerly</li><li>Added options <tt>allowNullBody</tt> and <tt>readLockMinLength</tt> to the <a shape="rect" href="file2.html" title="File2">File</a> and <a shape="rect" href="ftp2.html" title="FTP2">FTP</a> components.</li><li>Made <tt>changed</tt> read lock strategy on <a shape="rect" href="ftp2.html" title="FTP2">FTP</a> g
 o faster (eg when the FTP server has a lot of files in the directory) if you enable the <tt>fastExistsCheck=true</tt> option as well. Notice that some FTP server may not support this.</li><li><a shape="rect" href="hl7.html" title="HL7">HL7</a> moves to HAPI 2.0 and supports using a dedicated Parser instance in the <a shape="rect" href="hl7.html" title="HL7">HL7</a> MLLP codec and DataFormat. Added "Terser" language and expression to be able to extract fields from a parsed message. <a shape="rect" href="hl7.html" title="HL7">HL7</a> now uses Apache Mina 2.x.</li><li>Add an option <tt>HttpMethodRestrict</tt> to restrict HTTP method in <a shape="rect" href="jetty.html" title="Jetty">Jetty</a> and <a shape="rect" href="servlet.html" title="SERVLET">SERVLET</a></li><li>Add support for selection of <a shape="rect" href="direct-vm.html" title="Direct-VM">Direct-VM</a> consumers by using ant-like path expression.</li><li>The <a shape="rect" href="pojo-producing.html" title="POJO Pro
 ducing">POJO Producing</a>, and <a shape="rect" href="pojo-consuming.html" title="POJO Consuming">POJO Consuming</a> with @Consume, @Produce, @EndpointInject now supports a new {{property} attribute to get the endpoint configuration from a bean property (eg using a getter method); this allows you to configure this on the bean using conventional bean configuration.</li><li>Testing with <tt>camel-test-blueprint</tt> on Windows no longer tries to cleanup after testing taking up 5 seconds and logging WARNs.</li><li>The <a shape="rect" href="file2.html" title="File2">File</a>, and <a shape="rect" href="ftp2.html" title="FTP2">FTP</a> components now support <tt>fileExist=Move</tt> option to move any existing files before writing a file.</li><li>Added option <tt>loadStatisticsEnabled</tt> on <a shape="rect" href="camel-jmx.html" title="Camel JMX">Camel JMX</a> to allow to disable load statistics if not needed (avoids a background thread being in use, to calculate the load stats).</
 li><li>Enabled "lazy connections" for <a shape="rect" href="xmpp.html" title="XMPP">XMPP</a> providers via the <tt>testConnectionOnStartup</tt> option</li><li>Added a connection monitor to detect and fix dropped <a shape="rect" href="xmpp.html" title="XMPP">XMPP</a> consumer connections at configurable <tt>connectionPollDelay</tt> intervals</li><li>Added an <tt>org.apache.camel.builder.ExchangeBuilder</tt> to build the <a shape="rect" href="exchange.html" title="Exchange">Exchange</a> using a builder pattern.</li><li>The <a shape="rect" href="camel-run-maven-goal.html" title="Camel Run Maven Goal">Camel Run Maven Goal</a> can now run <a shape="rect" href="cdi.html" title="CDI">CDI</a> applications.</li><li>The Camel <a shape="rect" href="cdi.html" title="CDI">CDI</a> component has improved a lot.</li><li>Added option <tt>allowRedeliveryWhileStopping</tt> to <a shape="rect" href="dead-letter-channel.html" title="Dead Letter Channel">error handlers</a> to control if redelivery
  is allowed during stopping/shutting down Camel or the route(s). Turning this option <tt>false</tt> allows to stop quicker by rejecting redelivery attempts.</li><li>Added support for specifying user info in Camel <a shape="rect" href="endpoint.html" title="Endpoint">Endpoint</a> urls, which contains the @ sign; now the @ sign can be given as is; without being encoded to %40.</li><li>Added robust connection support for <a shape="rect" href="jmx.html" title="JMX">JMX</a>. Optional <tt>testConnectionOnStartup</tt> allows a JMX consumer to attach to a JMX server that becomes available <em>after</em> the JMX endpoint starts; <tt>reconnectOnConnectionFailure</tt> enables re-connection of failed JMX connections.</li><li><a shape="rect" href="jaxb.html" title="JAXB">JAXB</a> and <a shape="rect" href="soap.html" title="SOAP">SOAP</a> data format now supports controlling namespace prefix mappings when marshalling (eg to avoid prefixes such as ns2, ns3, ns4 etc.)</li><li>Added support 
 for using raw uris when <a shape="rect" href="component.html" title="Component">Component</a>s create <a shape="rect" href="endpoint.html" title="Endpoint">Endpoint</a>s. This gives component writers full power in case their component has special syntax/notation for endpoint uri configurations.</li><li><a shape="rect" href="eip.html" title="EIP">EIP</a>s configured with custom <tt>AggregationStrategy</tt> will now strict check the custom strategy exists in the <a shape="rect" href="registry.html" title="Registry">Registry</a> and no longer fallback and use a default strategy if not.</li><li>Camel now logs on shutdown if any thread pools hasn't been properly shutdown, and will shutdown them as fail safe (can only be done for the thread pools Camel manages).</li><li>The buffer size of <a shape="rect" href="stream-caching.html" title="Stream caching">Stream caching</a> is now configurable.</li><li>Improved startup performance.</li><li>Added <a shape="rect" href="jms.html" title
 ="JMS">JMS</a> URI option <tt>messageListenerContainerFactoryRef</tt> which allows you to specify a <tt>MessageListenerContainerFactory</tt> to determine what <tt>org.springframework.jms.listener.AbstractMessageListenerContainer</tt> to use to consume messages.</li><li><a shape="rect" href="mqtt.html" title="MQTT">MQTT</a> producer now leverages the <a shape="rect" href="asynchronous-routing-engine.html" title="Asynchronous Routing Engine">Asynchronous Routing Engine</a></li><li>The <a shape="rect" href="netty.html" title="Netty">Netty</a> producer scales up and down much better by leveraging a channel pool.</li><li>Added new <a shape="rect" href="camel-maven-archetypes.html" title="Camel Maven Archetypes">Camel Maven Archetypes</a> for creating Camel and Groovy applications.</li><li>Camel now injects <tt>CamelContext</tt> on <tt>Language</tt> and <tt>DataFormat</tt> that implements <tt>CamelContextAware</tt></li><li>Thread pools in Camel with <tt>maximumQueueSize</tt> of 0 
 or negative will now not use a worker queue but do direct hand-over to thread instead.</li><li><a shape="rect" href="simple.html" title="Simple">Simple</a> unary operators for inc and dec must now have function on left hand side, to be parsed as unary function. Otherwise its now regarded as literal.</li><li>Custom assigned id's on Camel <a shape="rect" href="routes.html" title="Routes">Routes</a> is now validated on starting the routes, that they must be unique within the same CamelContext.</li><li>Added <tt>AbstractListAggregationStrategy</tt> abstract class to make it easier to <a shape="rect" href="aggregator2.html" title="Aggregator2">aggregate</a> into a List&lt;V&gt; using a custom <tt>AggregationStrategy</tt>.</li><li><a shape="rect" href="eip.html" title="EIP">EIP</a>s which support using <tt>AggregationStrategy</tt> now control the lifecycle of the strategy; allowing end users to do custom logic in the start/stop methods of their strategy implementation.</li><li>Add
 ed option <tt>includeSentJMSMessageID</tt> to <a shape="rect" href="jms.html" title="JMS">JMS</a> to allow to enrich Camel Message with the actual JMSMessageID for the sent message. Can be used by end users for logging purpose etc.</li><li>Added option <tt>allowShortLines</tt> and <tt>ignoreExtraColumns</tt> to <a shape="rect" href="flatpack-dataformat.html" title="Flatpack DataFormat">Flatpack data format</a>.</li><li><a shape="rect" href="mail.html" title="Mail">Mail</a> consumer now supports using search terms to filter mails by terms such as subject, from, body, sent date etc.</li><li>The cached script file in the <a shape="rect" href="language.html" title="Language">Language</a> component can now be cleared via JMX.</li><li>improved the karaf context-info command by adding a verbose mode to view endpoints list (now hidden by default) and adding stats on the number of active/inactive routes</li><li>Added support for <tt>UpdateList</tt>, <tt>DeleteList</tt> and <tt>Execut
 orType</tt> to <a shape="rect" href="mybatis.html" title="MyBatis">MyBatis</a> component.</li><li>Added support for easier configuration of using concurrent message listener consumer when doing request/reply over <a shape="rect" href="jms.html" title="JMS">JMS</a>, by leveraging the existing <tt>concurrentConsumers</tt> and <tt>maxConcurrentConsumers</tt> options.</li><li>Improved the <a shape="rect" href="smpp.html" title="SMPP">SMPP</a> consumer to expose more data by receiving a <tt>DeliverSM</tt> message.</li><li>Camels <a shape="rect" href="using-propertyplaceholder.html" title="Using PropertyPlaceholder">property placeholders</a> can now be used in route id / node id's in the routes in XML and Java DSLs, eg &lt;route id="<tt>coolName</tt>"&gt;</li><li>The thread name pattern can easily be configured on &lt;camelContext&gt; with the new threadNamePattern attribute</li><li>Camel now validates <span class="error">[Sea]</span> and <a shape="rect" href="vm.html" title="VM">
 VM</a> endpoints using same queue name, that if any queue size is in use, that size must match. As well Camel logs at INFO level when starting up the queues and the sizes. This allows end users to easily spot any issues if mistakenly using different queue sizes for the same queue names.</li></ul>
 
 
 
@@ -148,7 +148,7 @@
 
 <h2><a shape="rect" name="Camel2.11.0Release-Importantchangestoconsiderwhenupgrading"></a>Important changes to consider when upgrading</h2>
 
-<ul><li><tt>camel-mina2</tt> now uses <tt>OrderedThreadPoolExecutor</tt> by default. There is a new option <tt>orderedThreadPoolExecutor</tt> you can configure it to <tt>false</tt> to revert back to unordered if needed. If using SSL etc. then ordered is required to be used.</li><li><tt>camel-netty</tt> now uses <tt>OrderedMemoryAwareThreadPoolExecutor</tt> by default. There is a new option <tt>orderedThreadPoolExecutor</tt> you can configure it to false to revert back to unordered if needed. If using SSL etc. then ordered is required to be used.</li><li>The default value of the <tt>delay</tt> option on <a shape="rect" href="timer.html" title="Timer">Timer</a> has been changed from <tt>0</tt> to <tt>1000</tt></li><li>The default value of the <tt>convertLFtoCR</tt> option of the <a shape="rect" href="hl7.html" title="HL7">HL7</a> MLLP codec has been changed from <tt>true</tt> to <tt>false</tt>. Likewise, the <a shape="rect" href="hl7.html" title="HL7">HL7</a> DataFormat and Ty
 peConverter do not perform this conversion anymore.</li><li>The <a shape="rect" href="simple.html" title="Simple">Simple</a> language has limited its support for the escape character to only new line, carriage return and tab characters. This makes it easier to use back-slash characters in the <a shape="rect" href="simple.html" title="Simple">Simple</a> language without double escaping etc.</li><li><tt>camel-netty</tt> now requires <tt>commons-pool</tt> as dependency.</li><li>The <tt>maximumQueueSize</tt> of <a shape="rect" class="external-link" href="http://camel.apache.org/threading-model.html">Thread Pools</a> and <a shape="rect" class="external-link" href="http://camel.apache.org/threading-model.html">Thread Pool Profiles</a> with values 0 or negative now means disable the worker queue, and use direct-handover. If you want an unbounded queue size, then set the <tt>maximumQueueSize</tt> to <tt>Integer.MAX_VALUE</tt> which was what the previous code did.</li><li>Custom assi
 gned id's on Camel <a shape="rect" href="routes.html" title="Routes">Routes</a> is now validated on starting the routes, that they must be unique within the same CamelContext.</li><li><tt>camel-blueprint</tt> now requires Apache Aries 1.0, and OSGi 4.3.0.</li><li>Removed @deprecated classes form <tt>camel-spring</tt> in the <tt>org.apache.camel.component</tt> package which was causing split-package issue with OSGi. Component authors who are using these @deprecated classes, should migrate to use equivalent classes from <tt>camel-core</tt> in the same package.</li><li>The default Spring version is upgraded from 3.0.7 to 3.1.3 out of the box.</li></ul>
+<ul><li><tt>camel-mina2</tt> now uses <tt>OrderedThreadPoolExecutor</tt> by default. There is a new option <tt>orderedThreadPoolExecutor</tt> you can configure it to <tt>false</tt> to revert back to unordered if needed. If using SSL etc. then ordered is required to be used.</li><li><tt>camel-netty</tt> now uses <tt>OrderedMemoryAwareThreadPoolExecutor</tt> by default. There is a new option <tt>orderedThreadPoolExecutor</tt> you can configure it to false to revert back to unordered if needed. If using SSL etc. then ordered is required to be used.</li><li>The default value of the <tt>delay</tt> option on <a shape="rect" href="timer.html" title="Timer">Timer</a> has been changed from <tt>0</tt> to <tt>1000</tt></li><li>The default value of the <tt>convertLFtoCR</tt> option of the <a shape="rect" href="hl7.html" title="HL7">HL7</a> MLLP codec has been changed from <tt>true</tt> to <tt>false</tt>. Likewise, the <a shape="rect" href="hl7.html" title="HL7">HL7</a> DataFormat and Ty
 peConverter do not perform this conversion anymore.</li><li>The <a shape="rect" href="simple.html" title="Simple">Simple</a> language has limited its support for the escape character to only new line, carriage return and tab characters. This makes it easier to use back-slash characters in the <a shape="rect" href="simple.html" title="Simple">Simple</a> language without double escaping etc.</li><li><tt>camel-netty</tt> now requires <tt>commons-pool</tt> as dependency.</li><li>The <tt>maximumQueueSize</tt> of <a shape="rect" class="external-link" href="http://camel.apache.org/threading-model.html">Thread Pools</a> and <a shape="rect" class="external-link" href="http://camel.apache.org/threading-model.html">Thread Pool Profiles</a> with values 0 or negative now means disable the worker queue, and use direct-handover. If you want an unbounded queue size, then set the <tt>maximumQueueSize</tt> to <tt>Integer.MAX_VALUE</tt> which was what the previous code did.</li><li>Custom assi
 gned id's on Camel <a shape="rect" href="routes.html" title="Routes">Routes</a> is now validated on starting the routes, that they must be unique within the same CamelContext.</li><li><tt>camel-blueprint</tt> now requires Apache Aries 1.0, and OSGi 4.3.0.</li><li>Removed @deprecated classes form <tt>camel-spring</tt> in the <tt>org.apache.camel.component</tt> package which was causing split-package issue with OSGi. Component authors who are using these @deprecated classes, should migrate to use equivalent classes from <tt>camel-core</tt> in the same package.</li><li>The default Spring version is upgraded from 3.0.7 to 3.1.3 out of the box.</li><li>Camel now validates <span class="error">[Sea]</span> and <a shape="rect" href="vm.html" title="VM">VM</a> endpoints using same queue name, that if any queue size is in use, that size must match. As well Camel logs at INFO level when starting up the queues and the sizes. This allows end users to easily spot any issues if mistakenly 
 using different queue sizes for the same queue names.</li></ul>
 
 
 <h2><a shape="rect" name="Camel2.11.0Release-Notice"></a>Notice</h2>

Modified: websites/production/camel/content/seda.html
==============================================================================
--- websites/production/camel/content/seda.html (original)
+++ websites/production/camel/content/seda.html Sun Nov 25 15:23:33 2012
@@ -99,7 +99,7 @@ seda:someName[?options]
 
 <h3><a shape="rect" name="SEDA-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"> Since </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>size</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> The maximum capacity of the SEDA queue (i.e., the number of messages it can hold). The default value in Camel 2.2 or older is <tt>1000</tt>. From Camel 2.3 onwards, the size is unbounded by default. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>concurrentConsumers</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>1</tt> </td><td colspan="1" rowspan="
 1" class="confluenceTd"> Number of concurrent threads processing exchanges. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>waitForTaskToComplete</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>IfReplyExpected</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Option to specify whether the caller should wait for the async task to complete or not before continuing. The following three options are supported: <tt>Always</tt>, <tt>Never</tt> or <tt>IfReplyExpected</tt>. The first two values are self-explanatory. The last value, <tt>IfReplyExpected</tt>, will only wait if the message is <a shape="rect" href="request-reply.html" title="Request Reply">Request Reply</a> based. The default option is <tt>IfReplyExpected</tt>. See more information about <a shape="rect" href="async.html" title="Async">Async</a> messaging. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"
 > <tt>timeout</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>30000</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Timeout (in milliseconds) before a SEDA producer will stop waiting for an asynchronous task to complete. See <tt>waitForTaskToComplete</tt> and <a shape="rect" href="async.html" title="Async">Async</a> for more details. In <b>Camel 2.2</b> you can now disable timeout by using 0 or a negative value. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>multipleConsumers</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>2.2</b> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies whether multiple consumers are allowed. If enabled, you can use <a shape="rect" href="seda.html" title="SEDA">SEDA</a> for <a shape="rect" class="external-link" href="http://en.wikipedia.org/wi
 ki/Publish%E2%80%93subscribe_pattern" rel="nofollow">Publish-Subscribe</a> messaging. That is, you can send a message to the SEDA queue and have each consumer receive a copy of the message. When enabled, this option should be specified on every consumer endpoint. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>limitConcurrentConsumers</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>2.3</b> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>true</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Whether to limit the number of <tt>concurrentConsumers</tt> to the maximum of <tt>500</tt>. By default, an exception will be thrown if a SEDA endpoint is configured with a greater number. You can disable that check by turning this option off. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>blockWhenFull</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>2.9</b> </td><td colspan="1" rowspan="1" class="c
 onfluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Whether a thread that sends messages to a full SEDA queue will block until the queue's capacity is no longer exhausted.  By default, an exception will be thrown stating that the queue is full. By enabling this option, the calling thread will instead block and wait until the message can be accepted. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>queueSize</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>2.9</b> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Component only:</b> The maximum default size (capacity of the number of messages it can hold) of the SEDA queue. This option is used if <tt>size</tt> is not in use. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>pollTimeout</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>2.9.3</b> </td><td colspan="1"
  rowspan="1" class="confluenceTd"> <tt>1000</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <em>Consumer only</em> &#8211; The timeout used when polling. When a timeout occurs, the consumer can check whether it is allowed to continue running. Setting a lower value allows the consumer to react more quickly upon shutdown. </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"> Since </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>size</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> The maximum capacity of the SEDA queue (i.e., the number of messages it can hold). The default value in Camel 2.2 or older is <tt>1000</tt>. From Camel 2.3 onwards, the size is unbounded by default. <b>Notice:</b> Mind if you use this option, then its the first endpoint being created with the queue name, that determines the size. To make sure all endpoints use same size, then configure the size option on all of them, or the first endpoint being
  created. From <b>Camel 2.11</b> onwards, a validation is taken place to ensure if using mixed queue sizes for the same queue name, Camel would detect this and fail creating the endpoint. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>concurrentConsumers</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>1</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Number of concurrent threads processing exchanges. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>waitForTaskToComplete</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>IfReplyExpected</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Option to specify whether the caller should wait for the async task to complete or not before continuing. The following three options are supported: <tt>Always</tt>, <tt>Never</tt> or <t
 t>IfReplyExpected</tt>. The first two values are self-explanatory. The last value, <tt>IfReplyExpected</tt>, will only wait if the message is <a shape="rect" href="request-reply.html" title="Request Reply">Request Reply</a> based. The default option is <tt>IfReplyExpected</tt>. See more information about <a shape="rect" href="async.html" title="Async">Async</a> messaging. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>timeout</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>30000</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Timeout (in milliseconds) before a SEDA producer will stop waiting for an asynchronous task to complete. See <tt>waitForTaskToComplete</tt> and <a shape="rect" href="async.html" title="Async">Async</a> for more details. In <b>Camel 2.2</b> you can now disable timeout by using 0 or a negative value. </td></tr><tr><td colspan="1" rowspan="1" class=
 "confluenceTd"> <tt>multipleConsumers</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>2.2</b> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies whether multiple consumers are allowed. If enabled, you can use <a shape="rect" href="seda.html" title="SEDA">SEDA</a> for <a shape="rect" class="external-link" href="http://en.wikipedia.org/wiki/Publish%E2%80%93subscribe_pattern" rel="nofollow">Publish-Subscribe</a> messaging. That is, you can send a message to the SEDA queue and have each consumer receive a copy of the message. When enabled, this option should be specified on every consumer endpoint. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>limitConcurrentConsumers</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>2.3</b> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>true</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> 
 Whether to limit the number of <tt>concurrentConsumers</tt> to the maximum of <tt>500</tt>. By default, an exception will be thrown if a SEDA endpoint is configured with a greater number. You can disable that check by turning this option off. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>blockWhenFull</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>2.9</b> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Whether a thread that sends messages to a full SEDA queue will block until the queue's capacity is no longer exhausted.  By default, an exception will be thrown stating that the queue is full. By enabling this option, the calling thread will instead block and wait until the message can be accepted. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>queueSize</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>2.9</b> </td><td colspan="1
 " rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Component only:</b> The maximum default size (capacity of the number of messages it can hold) of the SEDA queue. This option is used if <tt>size</tt> is not in use. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>pollTimeout</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>2.9.3</b> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>1000</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <em>Consumer only</em> &#8211; The timeout used when polling. When a timeout occurs, the consumer can check whether it is allowed to continue running. Setting a lower value allows the consumer to react more quickly upon shutdown. </td></tr></tbody></table>
 </div>
 </div>
 



Mime
View raw message