Author: buildbot
Date: Mon Nov 18 20:19:56 2013
New Revision: 887131
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/configuring-camel.html
websites/production/camel/content/how-do-i-import-routes-from-other-xml-files.html
websites/production/camel/content/jms.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 Mon Nov 18
20:19:56 2013
@@ -9556,6 +9556,17 @@ from("jms:SomeQueue?concurrentConsumers=
<ul><li>On the <tt>JmsComponent</tt>,</li><li>On the endpoint URI
or,</li><li>By invoking <tt>setConcurrentConsumers()</tt> directly on the
<tt>JmsEndpoint</tt>.</li></ul>
+<h4><a shape="rect"
name="BookComponentAppendix-ConcurrentConsumingwithasyncconsumer"></a>Concurrent
Consuming with async consumer</h4>
+
+<p>Notice that each concurrent consumer will only pickup the next available
message from the JMS broker, when the current message has been fully processed.
You can set the option <tt>asyncConsumer=true</tt> to let the consumer pickup
the next message from the JMS queue, while the previous message is being
processed asynchronously (by the <a shape="rect"
href="asynchronous-routing-engine.html" title="Asynchronous Routing
Engine">Asynchronous Routing Engine</a>). See more details in the table on top
of the page about the <tt>asyncConsumer</tt> option.</p>
+
+<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
+from("jms:SomeQueue?concurrentConsumers=20&asyncConsumer=true").
+ bean(MyClass.class);
+]]></script>
+</div></div>
+
<h3><a shape="rect"
name="BookComponentAppendix-RequestreplyoverJMS"></a>Request-reply over JMS</h3>
@@ -9574,6 +9585,8 @@ from("jms:SomeQueue?concurrentConsumers=
This consumer is a Spring <tt>DefaultMessageListenerContainer</tt> which
listen for replies. However it's fixed to 1 concurrent consumer.<br
clear="none">
That means replies will be processed in sequence as there are only 1 thread to
process the replies. If you want to process replies faster, then we need to use
concurrency. But <b>not</b> using the <tt>concurrentConsumer</tt> option. We
should use the <tt>threads</tt> from the Camel DSL instead, as shown in the
route below:</p>
+<div class="panelMacro"><table class="tipMacro"><colgroup span="1"><col
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1"
valign="top"><img align="middle"
src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif";
width="16" height="16" alt="" border="0"></td><td colspan="1"
rowspan="1">Instead of using threads, then use concurrentConsumers option if
using Camel 2.10.3 or better. See further below.</td></tr></table></div>
+
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
from(xxx)
@@ -9586,7 +9599,7 @@ from(xxx)
<p>In this route we instruct Camel to route replies <a shape="rect"
href="async.html" title="Async">asynchronously</a> using a thread pool with 5
threads.</p>
-<p>From Camel 2.10.3 onwards you can now configure the listener to use
concurrent threads using the <tt>concurrentConsumers</tt> and
<tt>maxConcurrentConsumers</tt> options. This allows you to easier configure
this in Camel as shown below:</p>
+<p>From <b>Camel 2.10.3</b> onwards you can now configure the listener to use
concurrent threads using the <tt>concurrentConsumers</tt> and
<tt>maxConcurrentConsumers</tt> options. This allows you to easier configure
this in Camel as shown below:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
from(xxx)
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 Mon Nov 18 20:19:56
2013
@@ -31139,6 +31139,17 @@ from("jms:SomeQueue?concurrentConsumers=
<ul><li>On the <tt>JmsComponent</tt>,</li><li>On the endpoint URI
or,</li><li>By invoking <tt>setConcurrentConsumers()</tt> directly on the
<tt>JmsEndpoint</tt>.</li></ul>
+<h4><a shape="rect"
name="BookInOnePage-ConcurrentConsumingwithasyncconsumer"></a>Concurrent
Consuming with async consumer</h4>
+
+<p>Notice that each concurrent consumer will only pickup the next available
message from the JMS broker, when the current message has been fully processed.
You can set the option <tt>asyncConsumer=true</tt> to let the consumer pickup
the next message from the JMS queue, while the previous message is being
processed asynchronously (by the <a shape="rect"
href="asynchronous-routing-engine.html" title="Asynchronous Routing
Engine">Asynchronous Routing Engine</a>). See more details in the table on top
of the page about the <tt>asyncConsumer</tt> option.</p>
+
+<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
+from("jms:SomeQueue?concurrentConsumers=20&asyncConsumer=true").
+ bean(MyClass.class);
+]]></script>
+</div></div>
+
<h3><a shape="rect" name="BookInOnePage-RequestreplyoverJMS"></a>Request-reply
over JMS</h3>
@@ -31157,6 +31168,8 @@ from("jms:SomeQueue?concurrentConsumers=
This consumer is a Spring <tt>DefaultMessageListenerContainer</tt> which
listen for replies. However it's fixed to 1 concurrent consumer.<br
clear="none">
That means replies will be processed in sequence as there are only 1 thread to
process the replies. If you want to process replies faster, then we need to use
concurrency. But <b>not</b> using the <tt>concurrentConsumer</tt> option. We
should use the <tt>threads</tt> from the Camel DSL instead, as shown in the
route below:</p>
+<div class="panelMacro"><table class="tipMacro"><colgroup span="1"><col
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1"
valign="top"><img align="middle"
src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif";
width="16" height="16" alt="" border="0"></td><td colspan="1"
rowspan="1">Instead of using threads, then use concurrentConsumers option if
using Camel 2.10.3 or better. See further below.</td></tr></table></div>
+
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
from(xxx)
@@ -31169,7 +31182,7 @@ from(xxx)
<p>In this route we instruct Camel to route replies <a shape="rect"
href="async.html" title="Async">asynchronously</a> using a thread pool with 5
threads.</p>
-<p>From Camel 2.10.3 onwards you can now configure the listener to use
concurrent threads using the <tt>concurrentConsumers</tt> and
<tt>maxConcurrentConsumers</tt> options. This allows you to easier configure
this in Camel as shown below:</p>
+<p>From <b>Camel 2.10.3</b> onwards you can now configure the listener to use
concurrent threads using the <tt>concurrentConsumers</tt> and
<tt>maxConcurrentConsumers</tt> options. This allows you to easier configure
this in Camel as shown below:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
from(xxx)
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/configuring-camel.html
==============================================================================
--- websites/production/camel/content/configuring-camel.html (original)
+++ websites/production/camel/content/configuring-camel.html Mon Nov 18
20:19:56 2013
@@ -221,6 +221,8 @@ myFtpPassword=se+re?t&23
<p>In <b>Camel 2.3</b> it is now possible to define routes outside
<tt><camelContext/></tt> which you do in a new
<tt><routeContext/></tt> tag.</p>
+<div class="panelMacro"><table class="infoMacro"><colgroup span="1"><col
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1"
valign="top"><img align="middle"
src="https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif";
width="16" height="16" alt="" border="0"></td><td colspan="1"
rowspan="1"><b>Notice:</b> When you use <routeContext> then they are
separated, and cannot reuse existing <onException>, <intercept>,
<dataFormats> and similar cross cutting functionality defined in the
<camelContext>. In other words the <routeContext> is currently
isolated. This may change in Camel 3.x.</td></tr></table></div>
+
<p>For example we could have a file named <tt>myCoolRoutes.xml</tt> which
contains a couple of routes as shown:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeHeader
panelHeader" style="border-bottom-width:
1px;"><b>myCoolRoutes.xml</b></div><div class="codeContent panelContent">
<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[
Modified:
websites/production/camel/content/how-do-i-import-routes-from-other-xml-files.html
==============================================================================
---
websites/production/camel/content/how-do-i-import-routes-from-other-xml-files.html
(original)
+++
websites/production/camel/content/how-do-i-import-routes-from-other-xml-files.html
Mon Nov 18 20:19:56 2013
@@ -91,6 +91,8 @@
<p>In <b>Camel 2.3</b> it is now possible to define routes outside
<tt><camelContext/></tt> which you do in a new
<tt><routeContext/></tt> tag.</p>
+<div class="panelMacro"><table class="infoMacro"><colgroup span="1"><col
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1"
valign="top"><img align="middle"
src="https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif";
width="16" height="16" alt="" border="0"></td><td colspan="1"
rowspan="1"><b>Notice:</b> When you use <routeContext> then they are
separated, and cannot reuse existing <onException>, <intercept>,
<dataFormats> and similar cross cutting functionality defined in the
<camelContext>. In other words the <routeContext> is currently
isolated. This may change in Camel 3.x.</td></tr></table></div>
+
<p>For example we could have a file named <tt>myCoolRoutes.xml</tt> which
contains a couple of routes as shown:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeHeader
panelHeader" style="border-bottom-width:
1px;"><b>myCoolRoutes.xml</b></div><div class="codeContent panelContent">
<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[
Modified: websites/production/camel/content/jms.html
==============================================================================
--- websites/production/camel/content/jms.html (original)
+++ websites/production/camel/content/jms.html Mon Nov 18 20:19:56 2013
@@ -434,6 +434,17 @@ from("jms:SomeQueue?concurrentConsumers=
<ul><li>On the <tt>JmsComponent</tt>,</li><li>On the endpoint URI
or,</li><li>By invoking <tt>setConcurrentConsumers()</tt> directly on the
<tt>JmsEndpoint</tt>.</li></ul>
+<h4><a shape="rect"
name="JMS-ConcurrentConsumingwithasyncconsumer"></a>Concurrent Consuming with
async consumer</h4>
+
+<p>Notice that each concurrent consumer will only pickup the next available
message from the JMS broker, when the current message has been fully processed.
You can set the option <tt>asyncConsumer=true</tt> to let the consumer pickup
the next message from the JMS queue, while the previous message is being
processed asynchronously (by the <a shape="rect"
href="asynchronous-routing-engine.html" title="Asynchronous Routing
Engine">Asynchronous Routing Engine</a>). See more details in the table on top
of the page about the <tt>asyncConsumer</tt> option.</p>
+
+<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
+from("jms:SomeQueue?concurrentConsumers=20&asyncConsumer=true").
+ bean(MyClass.class);
+]]></script>
+</div></div>
+
<h3><a shape="rect" name="JMS-RequestreplyoverJMS"></a>Request-reply over
JMS</h3>
@@ -452,6 +463,8 @@ from("jms:SomeQueue?concurrentConsumers=
This consumer is a Spring <tt>DefaultMessageListenerContainer</tt> which
listen for replies. However it's fixed to 1 concurrent consumer.<br
clear="none">
That means replies will be processed in sequence as there are only 1 thread to
process the replies. If you want to process replies faster, then we need to use
concurrency. But <b>not</b> using the <tt>concurrentConsumer</tt> option. We
should use the <tt>threads</tt> from the Camel DSL instead, as shown in the
route below:</p>
+<div class="panelMacro"><table class="tipMacro"><colgroup span="1"><col
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1"
valign="top"><img align="middle"
src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif";
width="16" height="16" alt="" border="0"></td><td colspan="1"
rowspan="1">Instead of using threads, then use concurrentConsumers option if
using Camel 2.10.3 or better. See further below.</td></tr></table></div>
+
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><
![https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif"](https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif"){kind=link}
![https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif"](https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif"){kind=link}