Author: buildbot
Date: Fri Nov 25 10:21:01 2016
New Revision: 1001628
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-219-release.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 Fri Nov 25
10:21:01 2016
@@ -621,8 +621,8 @@ cometds://localhost:8443/service/mychann
<div class="confluence-information-macro-body">
<p>When using CXF in streaming modes (see DataFormat option), then also read
about <a shape="rect" href="stream-caching.html">Stream caching</a>.</p>
</div>
-</div><p>The <strong>cxf:</strong> component provides integration with <a
shape="rect" href="http://cxf.apache.org";>Apache CXF</a> for connecting to
JAX-WS services hosted in CXF.</p><p><style type="text/css">/**/
div.rbtoc1478859561625 {padding: 0px;} div.rbtoc1478859561625 ul {list-style:
disc;margin-left: 0px;} div.rbtoc1478859561625 li {margin-left:
0px;padding-left: 0px;} /**/</style>
- </p><div class="toc-macro rbtoc1478859561625">
+</div><p>The <strong>cxf:</strong> component provides integration with <a
shape="rect" href="http://cxf.apache.org";>Apache CXF</a> for connecting to
JAX-WS services hosted in CXF.</p><p><style type="text/css">/**/
div.rbtoc1480069090727 {padding: 0px;} div.rbtoc1480069090727 ul {list-style:
disc;margin-left: 0px;} div.rbtoc1480069090727 li {margin-left:
0px;padding-left: 0px;} /**/</style>
+ </p><div class="toc-macro rbtoc1480069090727">
<ul class="toc-indentation"><li><a shape="rect"
href="#BookComponentAppendix-CXFComponent">CXF Component</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#BookComponentAppendix-URIformat">URI format</a></li><li><a shape="rect"
href="#BookComponentAppendix-Options">Options</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#BookComponentAppendix-Thedescriptionsofthedataformats">The descriptions
of the dataformats</a>
@@ -3086,7 +3086,7 @@ cometds://localhost:8443/service/mychann
</div>
</div><p>The options are divided into two tables, the first one contains the
most common options. The second table contains the less common and more
advanced options.</p><h4 id="BookComponentAppendix-CommonOptions">Common
Options</h4><p> </p><div class="confluenceTableSmall">
<div class="table-wrap">
- <table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Option</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Default Value</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>clientId</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Sets the JMS client ID to use.
Note that this value, if specified, must be unique and can only be used by a
single JMS connection instance. It is typically only required for durable topic
subscriptions. You may prefer to use <a shape="rect" class="external-link"
href="http://activemq.apache.org/virtual-destinations.html";>Virtual Topics</a>
instead.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>concurrentConsumers</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>
1</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Specifies
the default number of concurrent consumers.</p><p>From <strong>Camel
2.10.3</strong>: this option can also be used when doing request/reply over
JMS.</p><p>From <strong>Camel 2.16</strong>: there is a new
<strong><code>replyToConcurrentConsumers</code></strong>.</p><p>See the
<strong><code>maxMessagesPerTask</code></strong> option to control dynamic
scaling up/down of threads.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>disableReplyTo</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>When <strong><code>true</code></strong>, a
producer will behave like a <strong><code>InOnly</code></strong> exchange
with the exception that <strong><code>JMSReplyTo</code></strong> header is sent
out and not be suppressed like in the case of
<strong><code>InOnly</code></strong>. Like <strong><co
de>InOnly</code></strong> the producer will not wait for a reply. A consumer
with this flag will behave like <strong><code>InOnly</code></strong>. This
feature can be used to bridge <strong><code>InOut</code></strong> requests to
another queue so that a route on the other queue will send it´s response
directly back to the original
<strong><code>JMSReplyTo</code></strong>.</p></td></tr><tr><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>durableSubscriptionName</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The durable subscriber name for
specifying durable topic subscriptions. The
<strong><code>clientId</code></strong> option <strong>must</strong> be
configured as well.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>maxConcurrentConsumers</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>1</code></p></td><td
colspan="1" ro
wspan="1" class="confluenceTd"><p>Specifies the maximum number of concurrent
consumers.</p><p>From <strong>Camel 2.10.3</strong>: this option can also be
used when doing request/reply over JMS. <span> </span></p><p><span>From
</span><strong>Camel 2.16</strong><span>: there is a new
<strong><code>replyToMaxConcurrentConsumers</code></strong>. </span></p><p>See
also the <strong><code>maxMessagesPerTask</code></strong> option to control
dynamic scaling up/down of threads.</p><p>The
<strong><code>maxMessagesPerTask</code></strong><span> option <em>must</em> be
set to an integer greater than <strong><code>0</code></strong> for threads
to scale down. Otherwise, the number of threads will remain at
<span><strong><code>maxConcurrentConsumers</code></strong> until
shutdown.</span></span></p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>maxMessagesPerTask</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>-1</code></p></td><td colspan=
"1" rowspan="1" class="confluenceTd"><p>The number of messages a task can
receive after which it's terminated. The default,
<strong><code>-1</code></strong>, is unlimited.</p><p>If you use a range for
concurrent consumers
e.g., <strong><code>concurrentConsumers</code></strong> <code><</code>
<strong><code>maxConcurrentConsumers</code></strong> then this option can be
used to set a value to e.g., <strong><code>100</code></strong> to control how
fast the consumers will shrink when less work is required.</p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>preserveMessageQos</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Set to <strong><code>true</code></strong>,
if you want to send message using the QoS settings specified on the message,
instead of the QoS settings on the JMS endpoint. The following headers are
considered:</p>
+ <table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Option</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Default Value</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>clientId</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Sets the JMS client ID to use.
Note that this value, if specified, must be unique and can only be used by a
single JMS connection instance. It is typically only required for durable topic
subscriptions. You may prefer to use <a shape="rect" class="external-link"
href="http://activemq.apache.org/virtual-destinations.html";>Virtual Topics</a>
instead.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>concurrentConsumers</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>
1</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Specifies
the default number of concurrent consumers.</p><p>From <strong>Camel
2.10.3</strong>: this option can also be used when doing request/reply over
JMS.</p><p>From <strong>Camel 2.16</strong>: there is a new
<strong><code>replyToConcurrentConsumers</code></strong>.</p><p>See the
<strong><code>maxMessagesPerTask</code></strong> option to control dynamic
scaling up/down of threads.</p><p>When using ActiveMQ beware that the default
prefetch policy loads 1000 messages per consumer. See <a shape="rect"
class="external-link"
href="http://activemq.apache.org/what-is-the-prefetch-limit-for.html";>What is
the prefetch limit</a> on how to change this.</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>disableReplyTo</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>When
<strong><code>true</code></stro
ng>, a producer will behave like a <strong><code>InOnly</code></strong>
exchange with the exception that <strong><code>JMSReplyTo</code></strong>
header is sent out and not be suppressed like in the case of
<strong><code>InOnly</code></strong>. Like <strong><code>InOnly</code></strong>
the producer will not wait for a reply. A consumer with this flag will behave
like <strong><code>InOnly</code></strong>. This feature can be used to bridge
<strong><code>InOut</code></strong> requests to another queue so that a route
on the other queue will send it´s response directly back to the original
<strong><code>JMSReplyTo</code></strong>.</p></td></tr><tr><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>durableSubscriptionName</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The durable subscriber name for
specifying durable topic subscriptions. The <strong><code>clientId</code></
strong> option <strong>must</strong> be configured as
well.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>maxConcurrentConsumers</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>1</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Specifies the maximum number of
concurrent consumers.</p><p>From <strong>Camel 2.10.3</strong>: this option can
also be used when doing request/reply over JMS.
<span> </span></p><p><span>From </span><strong>Camel 2.16</strong><span>:
there is a new <strong><code>replyToMaxConcurrentConsumers</code></strong>.
</span></p><p>See also the <strong><code>maxMessagesPerTask</code></strong>
option to control dynamic scaling up/down of threads.</p><p>The
<strong><code>maxMessagesPerTask</code></strong><span> option <em>must</em> be
set to an integer greater than <strong><code>0</code></strong> for threads
to scale down. Otherwise, the number of threads will remain at
<span><strong><code>
maxConcurrentConsumers</code></strong> until
shutdown.</span></span></p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>maxMessagesPerTask</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>-1</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>The number of messages a task can receive
after which it's terminated. The default, <strong><code>-1</code></strong>, is
unlimited.</p><p>If you use a range for concurrent consumers
e.g., <strong><code>concurrentConsumers</code></strong> <code><</code>
<strong><code>maxConcurrentConsumers</code></strong> then this option can be
used to set a value to e.g., <strong><code>100</code></strong> to control how
fast the consumers will shrink when less work is required.</p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>preserveMessageQos</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1"
rowspan
="1" class="confluenceTd"><p>Set to <strong><code>true</code></strong>, if you
want to send message using the QoS settings specified on the message, instead
of the QoS settings on the JMS endpoint. The following headers are
considered:</p>
<ul><li><strong><code>JMSPriority</code></strong></li><li><strong><code>JMSDeliveryMode</code></strong></li><li><strong><code>JMSExpiration</code></strong>.</li></ul><p>You
can provide some or all of them.</p><p>If not provided, Camel will fall back
to use the values from the endpoint instead. So, when using this option, the
headers override the values from the endpoint.</p><p>The
<strong><code>explicitQosEnabled</code></strong> option, by contrast, will only
use options set on the endpoint, and not values from the message
header.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>replyTo</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Provides an
explicit <strong><code>ReplyTo</code></strong> destination, which
overrides any incoming value of
<strong><code>Message.getJMSReplyTo()</code></strong>.</p><p>If you do <a
shape="rect" href="request-reply.html
">Request Reply</a> over JMS then <strong>make sure</strong> to read the
section <em>Request-reply over JMS</em> further below for more details, and the
<strong><code>replyToType</code></strong> option as well.</p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>replyToConcurrentConsumers</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>1</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.16</strong>:
Specifies the default number of concurrent consumers when doing request/reply
over JMS.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>replyToMaxConcurrentConsumers</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>1</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.16</strong>:
Specifies the maximum number of concurrent consumers when doing request/reply
over JMS.</p><p>See the <strong><code>maxMessagesPerTask</code></s
trong> option to control dynamic scaling up/down of
threads.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>replyToOnTimeoutMaxConcurrentConsumers</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>1</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.17.2</strong>:
Specifies the maximum number of concurrent consumers for continue routing when
timeout occurred when using request/reply over JMS.</p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>replyToOverride</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><strong>Camel 2.15:</strong> Provides an
explicit <strong><code>ReplyTo</code></strong> destination in the JMS
message, which overrides the setting of <strong><code>ReplyTo</code></strong>.
It is useful if you want to forward the message to a remote Queue and receive
the reply
message from the <strong><code>ReplyTo</code></strong>
destination.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>replyToType</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><strong>Camel 2.9:</strong> Allows for
explicitly specifying which kind of strategy to use
for <strong><code>replyTo</code></strong> queues when doing request/reply
over JMS. Possible values are:</p>
<ul><li><strong><code>Temporary</code></strong></li><li><strong><code>Shared</code></strong></li><li><strong><code>Exclusive</code></strong></li></ul><p>By
default Camel will use <strong><code>Temporary</code></strong>
queues.</p><p>However if <strong><code>replyTo</code></strong> has been
configured, then <strong><code>Shared</code></strong> is used by default. This
option allows you to use exclusive queues instead of shared queues.</p><p>For
more details see below, and especially the notes about the implications if
running in a clustered environment, and the fact that
<strong><code>Shared</code></strong> reply queues has lower performance than
its alternatives <strong><code>Temporary</code></strong> and
<strong><code>Exclusive</code></strong>.</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>requestTimeout</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>20000</code></p></td><td
colspan="1" rowspan="1" class="confluenceT
d"><p><strong>Producer only:</strong> The timeout for waiting for a reply when
using the <strong><code>InOut</code></strong> <a shape="rect"
href="exchange-pattern.html">Exchange Pattern</a> (in milliseconds).</p><p>From
<strong>Camel 2.13/2.12.3</strong>: you can include the header
<strong><code>CamelJmsRequestTimeout</code></strong> to override this endpoint
configured timeout value, and thus have per message individual timeout
values.</p><p>See below in section <em>About time to live</em> for more
details. See also
the <strong><code>requestTimeoutCheckerInterval</code></strong>
option.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>selector</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Sets the JMS Selector, which is an SQL 92
predicate that is used to filter messages within the broker. You may have to
encode special characters like '<strong><co
de>='</code></strong>
as <strong><code>%3D</code></strong>.</p><p>Before<strong> Camel
2.3.0</strong>: this option was not supported
in <strong><code>CamelConsumerTemplate</code></strong>.</p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>timeToLive</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>When sending messages, specifies the
time-to-live of the message (in milliseconds).</p><p>See below in section
<em>About time to live</em> for more details.</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>transacted</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Specifies whether to use
transacted mode for sending/receiving messages using
the <strong><code>InOnly</code></strong> <a shape="rect"
href="exchange-pattern.html">Exchange
Pattern</a>.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>testConnectionOnStartup</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.1:</strong>
Specifies whether to test the connection on startup. This ensures that when
Camel starts that all the JMS consumers have a valid connection to the JMS
broker. If a connection cannot be granted then Camel throws an exception on
startup. This ensures that Camel is not started with failed
connections.</p><p>From <strong>Camel 2.8</strong>: also the JMS producers is
tested as well.</p></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 Fri Nov 25 10:21:01
2016
@@ -3966,11 +3966,11 @@ The tutorial has been designed in two pa
While not actual tutorials you might find working through the source of the
various <a shape="rect" href="examples.html">Examples</a> useful.</li></ul>
<h2 id="BookInOnePage-TutorialonSpringRemotingwithJMS">Tutorial on Spring
Remoting with JMS</h2><p> </p><div class="confluence-information-macro
confluence-information-macro-information"><p class="title">Thanks</p><span
class="aui-icon aui-icon-small aui-iconfont-info
confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>This tutorial was kindly donated
to Apache Camel by Martin Gilday.</p></div></div><h2
id="BookInOnePage-Preface">Preface</h2><p>This tutorial aims to guide the
reader through the stages of creating a project which uses Camel to facilitate
the routing of messages from a JMS queue to a <a shape="rect"
class="external-link" href="http://www.springramework.org";
rel="nofollow">Spring</a> service. The route works in a synchronous fashion
returning a response to the client.</p><p><style type="text/css">/*<![CDATA[*/
-div.rbtoc1479813563181 {padding: 0px;}
-div.rbtoc1479813563181 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1479813563181 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1480069135697 {padding: 0px;}
+div.rbtoc1480069135697 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1480069135697 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1479813563181">
+/*]]>*/</style></p><div class="toc-macro rbtoc1480069135697">
<ul class="toc-indentation"><li><a shape="rect"
href="#BookInOnePage-TutorialonSpringRemotingwithJMS">Tutorial on Spring
Remoting with JMS</a></li><li><a shape="rect"
href="#BookInOnePage-Preface">Preface</a></li><li><a shape="rect"
href="#BookInOnePage-Prerequisites">Prerequisites</a></li><li><a shape="rect"
href="#BookInOnePage-Distribution">Distribution</a></li><li><a shape="rect"
href="#BookInOnePage-About">About</a></li><li><a shape="rect"
href="#BookInOnePage-CreatetheCamelProject">Create the Camel Project</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#BookInOnePage-UpdatethePOMwithDependencies">Update the POM with
Dependencies</a></li></ul>
</li><li><a shape="rect" href="#BookInOnePage-WritingtheServer">Writing the
Server</a>
@@ -6085,11 +6085,11 @@ So we completed the last piece in the pi
<p>This example has been removed from <strong>Camel 2.9</strong> onwards.
Apache Axis 1.4 is a very old and unsupported framework. We encourage users to
use <a shape="rect" href="cxf.html">CXF</a> instead of Axis.</p></div></div>
<style type="text/css">/*<![CDATA[*/
-div.rbtoc1479813563997 {padding: 0px;}
-div.rbtoc1479813563997 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1479813563997 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1480069136033 {padding: 0px;}
+div.rbtoc1480069136033 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1480069136033 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style><div class="toc-macro rbtoc1479813563997">
+/*]]>*/</style><div class="toc-macro rbtoc1480069136033">
<ul class="toc-indentation"><li><a shape="rect"
href="#BookInOnePage-TutorialusingAxis1.4withApacheCamel">Tutorial using Axis
1.4 with Apache Camel</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#BookInOnePage-Prerequisites">Prerequisites</a></li><li><a shape="rect"
href="#BookInOnePage-Distribution">Distribution</a></li><li><a shape="rect"
href="#BookInOnePage-Introduction">Introduction</a></li><li><a shape="rect"
href="#BookInOnePage-SettinguptheprojecttorunAxis">Setting up the project to
run Axis</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#BookInOnePage-Maven2">Maven 2</a></li><li><a shape="rect"
href="#BookInOnePage-wsdl">wsdl</a></li><li><a shape="rect"
href="#BookInOnePage-ConfiguringAxis">Configuring Axis</a></li><li><a
shape="rect" href="#BookInOnePage-RunningtheExample">Running the
Example</a></li></ul>
@@ -14323,8 +14323,8 @@ cometds://localhost:8443/service/mychann
<div class="confluence-information-macro-body">
<p>When using CXF in streaming modes (see DataFormat option), then also read
about <a shape="rect" href="stream-caching.html">Stream caching</a>.</p>
</div>
-</div><p>The <strong>cxf:</strong> component provides integration with <a
shape="rect" href="http://cxf.apache.org";>Apache CXF</a> for connecting to
JAX-WS services hosted in CXF.</p><p><style type="text/css">/**/
div.rbtoc1479813587300 {padding: 0px;} div.rbtoc1479813587300 ul {list-style:
disc;margin-left: 0px;} div.rbtoc1479813587300 li {margin-left:
0px;padding-left: 0px;} /**/</style>
- </p><div class="toc-macro rbtoc1479813587300">
+</div><p>The <strong>cxf:</strong> component provides integration with <a
shape="rect" href="http://cxf.apache.org";>Apache CXF</a> for connecting to
JAX-WS services hosted in CXF.</p><p><style type="text/css">/**/
div.rbtoc1480069174922 {padding: 0px;} div.rbtoc1480069174922 ul {list-style:
disc;margin-left: 0px;} div.rbtoc1480069174922 li {margin-left:
0px;padding-left: 0px;} /**/</style>
+ </p><div class="toc-macro rbtoc1480069174922">
<ul class="toc-indentation"><li><a shape="rect"
href="#BookInOnePage-CXFComponent">CXF Component</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#BookInOnePage-URIformat">URI format</a></li><li><a shape="rect"
href="#BookInOnePage-Options">Options</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#BookInOnePage-Thedescriptionsofthedataformats">The descriptions of the
dataformats</a>
@@ -16788,7 +16788,7 @@ cometds://localhost:8443/service/mychann
</div>
</div><p>The options are divided into two tables, the first one contains the
most common options. The second table contains the less common and more
advanced options.</p><h4 id="BookInOnePage-CommonOptions">Common
Options</h4><p> </p><div class="confluenceTableSmall">
<div class="table-wrap">
- <table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Option</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Default Value</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>clientId</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Sets the JMS client ID to use.
Note that this value, if specified, must be unique and can only be used by a
single JMS connection instance. It is typically only required for durable topic
subscriptions. You may prefer to use <a shape="rect" class="external-link"
href="http://activemq.apache.org/virtual-destinations.html";>Virtual Topics</a>
instead.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>concurrentConsumers</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>
1</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Specifies
the default number of concurrent consumers.</p><p>From <strong>Camel
2.10.3</strong>: this option can also be used when doing request/reply over
JMS.</p><p>From <strong>Camel 2.16</strong>: there is a new
<strong><code>replyToConcurrentConsumers</code></strong>.</p><p>See the
<strong><code>maxMessagesPerTask</code></strong> option to control dynamic
scaling up/down of threads.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>disableReplyTo</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>When <strong><code>true</code></strong>, a
producer will behave like a <strong><code>InOnly</code></strong> exchange
with the exception that <strong><code>JMSReplyTo</code></strong> header is sent
out and not be suppressed like in the case of
<strong><code>InOnly</code></strong>. Like <strong><co
de>InOnly</code></strong> the producer will not wait for a reply. A consumer
with this flag will behave like <strong><code>InOnly</code></strong>. This
feature can be used to bridge <strong><code>InOut</code></strong> requests to
another queue so that a route on the other queue will send it´s response
directly back to the original
<strong><code>JMSReplyTo</code></strong>.</p></td></tr><tr><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>durableSubscriptionName</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The durable subscriber name for
specifying durable topic subscriptions. The
<strong><code>clientId</code></strong> option <strong>must</strong> be
configured as well.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>maxConcurrentConsumers</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>1</code></p></td><td
colspan="1" ro
wspan="1" class="confluenceTd"><p>Specifies the maximum number of concurrent
consumers.</p><p>From <strong>Camel 2.10.3</strong>: this option can also be
used when doing request/reply over JMS. <span> </span></p><p><span>From
</span><strong>Camel 2.16</strong><span>: there is a new
<strong><code>replyToMaxConcurrentConsumers</code></strong>. </span></p><p>See
also the <strong><code>maxMessagesPerTask</code></strong> option to control
dynamic scaling up/down of threads.</p><p>The
<strong><code>maxMessagesPerTask</code></strong><span> option <em>must</em> be
set to an integer greater than <strong><code>0</code></strong> for threads
to scale down. Otherwise, the number of threads will remain at
<span><strong><code>maxConcurrentConsumers</code></strong> until
shutdown.</span></span></p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>maxMessagesPerTask</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>-1</code></p></td><td colspan=
"1" rowspan="1" class="confluenceTd"><p>The number of messages a task can
receive after which it's terminated. The default,
<strong><code>-1</code></strong>, is unlimited.</p><p>If you use a range for
concurrent consumers
e.g., <strong><code>concurrentConsumers</code></strong> <code><</code>
<strong><code>maxConcurrentConsumers</code></strong> then this option can be
used to set a value to e.g., <strong><code>100</code></strong> to control how
fast the consumers will shrink when less work is required.</p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>preserveMessageQos</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Set to <strong><code>true</code></strong>,
if you want to send message using the QoS settings specified on the message,
instead of the QoS settings on the JMS endpoint. The following headers are
considered:</p>
+ <table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Option</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Default Value</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>clientId</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Sets the JMS client ID to use.
Note that this value, if specified, must be unique and can only be used by a
single JMS connection instance. It is typically only required for durable topic
subscriptions. You may prefer to use <a shape="rect" class="external-link"
href="http://activemq.apache.org/virtual-destinations.html";>Virtual Topics</a>
instead.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>concurrentConsumers</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>
1</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Specifies
the default number of concurrent consumers.</p><p>From <strong>Camel
2.10.3</strong>: this option can also be used when doing request/reply over
JMS.</p><p>From <strong>Camel 2.16</strong>: there is a new
<strong><code>replyToConcurrentConsumers</code></strong>.</p><p>See the
<strong><code>maxMessagesPerTask</code></strong> option to control dynamic
scaling up/down of threads.</p><p>When using ActiveMQ beware that the default
prefetch policy loads 1000 messages per consumer. See <a shape="rect"
class="external-link"
href="http://activemq.apache.org/what-is-the-prefetch-limit-for.html";>What is
the prefetch limit</a> on how to change this.</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>disableReplyTo</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>When
<strong><code>true</code></stro
ng>, a producer will behave like a <strong><code>InOnly</code></strong>
exchange with the exception that <strong><code>JMSReplyTo</code></strong>
header is sent out and not be suppressed like in the case of
<strong><code>InOnly</code></strong>. Like <strong><code>InOnly</code></strong>
the producer will not wait for a reply. A consumer with this flag will behave
like <strong><code>InOnly</code></strong>. This feature can be used to bridge
<strong><code>InOut</code></strong> requests to another queue so that a route
on the other queue will send it´s response directly back to the original
<strong><code>JMSReplyTo</code></strong>.</p></td></tr><tr><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>durableSubscriptionName</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The durable subscriber name for
specifying durable topic subscriptions. The <strong><code>clientId</code></
strong> option <strong>must</strong> be configured as
well.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>maxConcurrentConsumers</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>1</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Specifies the maximum number of
concurrent consumers.</p><p>From <strong>Camel 2.10.3</strong>: this option can
also be used when doing request/reply over JMS.
<span> </span></p><p><span>From </span><strong>Camel 2.16</strong><span>:
there is a new <strong><code>replyToMaxConcurrentConsumers</code></strong>.
</span></p><p>See also the <strong><code>maxMessagesPerTask</code></strong>
option to control dynamic scaling up/down of threads.</p><p>The
<strong><code>maxMessagesPerTask</code></strong><span> option <em>must</em> be
set to an integer greater than <strong><code>0</code></strong> for threads
to scale down. Otherwise, the number of threads will remain at
<span><strong><code>
maxConcurrentConsumers</code></strong> until
shutdown.</span></span></p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>maxMessagesPerTask</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>-1</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>The number of messages a task can receive
after which it's terminated. The default, <strong><code>-1</code></strong>, is
unlimited.</p><p>If you use a range for concurrent consumers
e.g., <strong><code>concurrentConsumers</code></strong> <code><</code>
<strong><code>maxConcurrentConsumers</code></strong> then this option can be
used to set a value to e.g., <strong><code>100</code></strong> to control how
fast the consumers will shrink when less work is required.</p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>preserveMessageQos</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1"
rowspan
="1" class="confluenceTd"><p>Set to <strong><code>true</code></strong>, if you
want to send message using the QoS settings specified on the message, instead
of the QoS settings on the JMS endpoint. The following headers are
considered:</p>
<ul><li><strong><code>JMSPriority</code></strong></li><li><strong><code>JMSDeliveryMode</code></strong></li><li><strong><code>JMSExpiration</code></strong>.</li></ul><p>You
can provide some or all of them.</p><p>If not provided, Camel will fall back
to use the values from the endpoint instead. So, when using this option, the
headers override the values from the endpoint.</p><p>The
<strong><code>explicitQosEnabled</code></strong> option, by contrast, will only
use options set on the endpoint, and not values from the message
header.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>replyTo</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Provides an
explicit <strong><code>ReplyTo</code></strong> destination, which
overrides any incoming value of
<strong><code>Message.getJMSReplyTo()</code></strong>.</p><p>If you do <a
shape="rect" href="request-reply.html
">Request Reply</a> over JMS then <strong>make sure</strong> to read the
section <em>Request-reply over JMS</em> further below for more details, and the
<strong><code>replyToType</code></strong> option as well.</p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>replyToConcurrentConsumers</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>1</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.16</strong>:
Specifies the default number of concurrent consumers when doing request/reply
over JMS.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>replyToMaxConcurrentConsumers</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>1</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.16</strong>:
Specifies the maximum number of concurrent consumers when doing request/reply
over JMS.</p><p>See the <strong><code>maxMessagesPerTask</code></s
trong> option to control dynamic scaling up/down of
threads.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>replyToOnTimeoutMaxConcurrentConsumers</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>1</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.17.2</strong>:
Specifies the maximum number of concurrent consumers for continue routing when
timeout occurred when using request/reply over JMS.</p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>replyToOverride</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><strong>Camel 2.15:</strong> Provides an
explicit <strong><code>ReplyTo</code></strong> destination in the JMS
message, which overrides the setting of <strong><code>ReplyTo</code></strong>.
It is useful if you want to forward the message to a remote Queue and receive
the reply
message from the <strong><code>ReplyTo</code></strong>
destination.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>replyToType</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><strong>Camel 2.9:</strong> Allows for
explicitly specifying which kind of strategy to use
for <strong><code>replyTo</code></strong> queues when doing request/reply
over JMS. Possible values are:</p>
<ul><li><strong><code>Temporary</code></strong></li><li><strong><code>Shared</code></strong></li><li><strong><code>Exclusive</code></strong></li></ul><p>By
default Camel will use <strong><code>Temporary</code></strong>
queues.</p><p>However if <strong><code>replyTo</code></strong> has been
configured, then <strong><code>Shared</code></strong> is used by default. This
option allows you to use exclusive queues instead of shared queues.</p><p>For
more details see below, and especially the notes about the implications if
running in a clustered environment, and the fact that
<strong><code>Shared</code></strong> reply queues has lower performance than
its alternatives <strong><code>Temporary</code></strong> and
<strong><code>Exclusive</code></strong>.</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>requestTimeout</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>20000</code></p></td><td
colspan="1" rowspan="1" class="confluenceT
d"><p><strong>Producer only:</strong> The timeout for waiting for a reply when
using the <strong><code>InOut</code></strong> <a shape="rect"
href="exchange-pattern.html">Exchange Pattern</a> (in milliseconds).</p><p>From
<strong>Camel 2.13/2.12.3</strong>: you can include the header
<strong><code>CamelJmsRequestTimeout</code></strong> to override this endpoint
configured timeout value, and thus have per message individual timeout
values.</p><p>See below in section <em>About time to live</em> for more
details. See also
the <strong><code>requestTimeoutCheckerInterval</code></strong>
option.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>selector</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Sets the JMS Selector, which is an SQL 92
predicate that is used to filter messages within the broker. You may have to
encode special characters like '<strong><co
de>='</code></strong>
as <strong><code>%3D</code></strong>.</p><p>Before<strong> Camel
2.3.0</strong>: this option was not supported
in <strong><code>CamelConsumerTemplate</code></strong>.</p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>timeToLive</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>When sending messages, specifies the
time-to-live of the message (in milliseconds).</p><p>See below in section
<em>About time to live</em> for more details.</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>transacted</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Specifies whether to use
transacted mode for sending/receiving messages using
the <strong><code>InOnly</code></strong> <a shape="rect"
href="exchange-pattern.html">Exchange
Pattern</a>.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>testConnectionOnStartup</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.1:</strong>
Specifies whether to test the connection on startup. This ensures that when
Camel starts that all the JMS consumers have a valid connection to the JMS
broker. If a connection cannot be granted then Camel throws an exception on
startup. This ensures that Camel is not started with failed
connections.</p><p>From <strong>Camel 2.8</strong>: also the JMS producers is
tested as well.</p></td></tr></tbody></table>
</div>
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/camel-219-release.html
==============================================================================
--- websites/production/camel/content/camel-219-release.html (original)
+++ websites/production/camel/content/camel-219-release.html Fri Nov 25
10:21:01 2016
@@ -85,7 +85,7 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><h1
id="Camel2.19Release-Camel2.19.0Release(currentlyinprogress)">Camel 2.19.0
Release (currently in progress)</h1><div
style="padding-right:20px;float:left;margin-left:-20px;"><span
class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image
confluence-external-resource"
src="http://camel.apache.org/images/camel-box-small.png";
data-image-src="http://camel.apache.org/images/camel-box-small.png";></span></div><div
style="min-height:200px"> </div><h2
id="Camel2.19Release-NewandNoteworthy">New and Noteworthy</h2><p>Welcome to the
2.19.0 release which approx XXX issues resolved (new features, improvements and
bug fixes such
as...)</p><ul><li>Returning <code>null</code> from <a
shape="rect" href="bean.html">Bean</a> should work similar to
how <code>setBody</code> and <code>transform</code> works
when they set a <code>null</code> body.</li><li>The Camel Spring Boot
starter components
now have their auto configuration depends
on <code>org.apache.camel.springboot.CamelAutoConfiguration</code> which
makes it easier writing unit tests where you can
exclude <code>org.apache.camel.springboot.CamelAutoConfiguration</code> to
turn off Camel Spring Boot auto configuration completely.</li><li>Camel now
supports OWASP dependency check maven plugin</li><li>Camel-Nats component now
supports TLS</li><li>Camel-Nats component now supports explicit flushing (with
timeout) of the connection</li><li>Camel-Metrics component now supports Gauge
type</li><li><a shape="rect" href="file2.html">File consumer</a> now
supports idempotent-changed and idempotent-rename read lock strategies for
clustering. </li><li>Camel Catalog now supports custom runtime providers
that only includes the supported Camel components, languages and data formats
running in that container. For example for Karaf or Spring Boot in the
camel-catalog-provider-karaf and camel-catalog-provider-sprin
gboot.</li><li>The <a shape="rect"
href="https://cwiki.apache.org/confluence/display/WW/bean";>bean</a> component
will when calling a method that returned an instance of
<code>Callable</code> now call that callable to obtain the chained result.
This allows to call Groovy functions/closures etc.</li><li>Failover <a
shape="rect" href="load-balancer.html">Load Balancer</a> with
inheritErrorHandler=false, now allows Camel's <a shape="rect"
href="error-handler.html">Error Handler</a> to react after the load balancer is
exhausted.</li></ul><p>Fixed these issues</p><ul><li>Fixed <a shape="rect"
href="hystrix-eip.html">Hystrix EIP</a> to also execute fallback if execution
was rejected or short-circuited or other reasons from
Hystrix. </li><li>Fixed adding new routes to running CamelContext and if
the new routes would fail to startup, then before these routes would "hang
around". Now only succesful started routes are added.</li><li>Adding or
removing routes that
starts from <a shape="rect" href="undertow.html">Undertow</a> no longer
restart the entire HTTP server</li><li><a shape="rect" href="vm.html">VM</a>
endpoint should prepare exchange with the CamelContext from the consumer and
not from cached endpoint which can be different</li><li>Fixed a bug when
using <a shape="rect" href="rest-dsl.html">Rest DSL</a> with <a
shape="rect" href="servlet.html">SERVLET</a> could cause a java.io.IOException:
Stream closed exception when using <a shape="rect"
href="bean.html">Bean</a> in the route. </li><li>Fixed an issue when
using <code>pipeline</code> in Java DSL not setting up the EIP correctly
which could lead to runtime route not as intended.</li><li>Fixed <a
shape="rect" href="dropbox.html">Dropbox</a> to use <a shape="rect"
href="stream-caching.html">Stream caching</a> to avoid reading entire file into
memory so Camel can process big files</li><li>Fixed Netty douhle buffer release
leak in <a shape="re
ct" href="netty4.html">Netty4</a> and <a shape="rect"
href="netty4-http.html">Netty4 HTTP</a></li></ul><h3
id="Camel2.19Release-New">New <a shape="rect"
href="enterprise-integration-patterns.html">Enterprise Integration
Patterns</a></h3><h3 id="Camel2.19Release-New.1">New <a shape="rect"
href="components.html">Components</a></h3><ul><li>camel-bonita - allow you
to communicate with a remote Bonita engine.</li><li>camel-google-pubsub - allow
you communicate with Google Cloud Pub/Sub</li></ul><h3
id="Camel2.19Release-NewDSL">New DSL</h3><h3
id="Camel2.19Release-NewAnnotations">New Annotations</h3><h3
id="Camel2.19Release-New.2">New <a shape="rect" href="data-format.html">Data
Format</a></h3><h3 id="Camel2.19Release-New.3">New <a shape="rect"
href="languages.html">Languages</a></h3><h3 id="Camel2.19Release-New.4">New <a
shape="rect" href="examples.html">Examples</a></h3><h3
id="Camel2.19Release-New.5">New <a shape="rect"
href="tutorials.html">Tutorials</a></h3><h2 id="Camel2.1
9Release-APIbreaking">API breaking</h2><h2
id="Camel2.19Release-KnownIssues">Known Issues</h2><h2
id="Camel2.19Release-Importantchangestoconsiderwhenupgrading">Important changes
to consider when upgrading</h2><ul><li>Camel now uses Karaf 4.x API and
therefore not possible to run on older Karaf versions</li><li>camel-spring-boot
now don't include prototype scoped beans when auto scanning for RouteBuilder
instances, which is how camel-spring works. You can turn this back using
the includeNonSingletons option.</li></ul><h2
id="Camel2.19Release-GettingtheDistributions">Getting the Distributions</h2><h3
id="Camel2.19Release-BinaryDistributions">Binary Distributions</h3><div
class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1"
rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p>PGP Signature file of
download</p></th></tr><tr><td col
span="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect"
class="external-link"
href="http://www.apache.org/dyn/closer.cgi/camel/apache-camel/x.y.x/apache-camel-x.y.x.zip";>apache-camel-x.y.x.zip</a></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect"
class="external-link"
href="http://www.apache.org/dist/camel/apache-camel/x.y.x/apache-camel-x.y.x.zip.asc";>apache-camel-x.y.x.zip.asc</a></p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin
Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a
shape="rect" class="external-link"
href="http://www.apache.org/dyn/closer.cgi/camel/apache-camel/x.y.x/apache-camel-x.y.x.tar.gz";>apache-camel-x.y.x.tar.gz</a></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect"
class="external-link"
href="http://www.apache.org/dist/camel/apache-camel/x.y.x/apache-camel-x.y.x.t
ar.gz.asc">apache-camel-x.y.x.tar.gz.asc</a></p></td></tr></tbody></table></div><div
class="confluence-information-macro
confluence-information-macro-information"><p class="title">The above URLs use
redirection</p><span class="aui-icon aui-icon-small aui-iconfont-info
confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>The above URLs use the Apache
Mirror system to redirect you to a suitable mirror for your download. Some
users have experienced issues with some versions of browsers (e.g. some Safari
browsers). If the download doesn't seem to work for you from the above URL then
try using <a shape="rect" class="external-link"
href="http://www.mozilla.com/en-US/firefox/";
rel="nofollow">FireFox</a></p></div></div><h3
id="Camel2.19Release-SourceDistributions">Source Distributions</h3><div
class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1"
rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1"
rowspan="1"
class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>Source (zip)</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect"
class="external-link"
href="http://www.apache.org/dyn/closer.cgi/camel/apache-camel/x.y.x/apache-camel-x.y.x-src.zip";>apache-camel-x.y.x-src.zip</a></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect"
class="external-link"
href="http://www.apache.org/dist/camel/apache-camel/x.y.x/apache-camel-x.y.x-src.zip.asc";>apache-camel-x.y.x-src.zip.asc</a></p></td></tr></tbody></table></div><h3
id="Camel2.19Release-GettingtheBinariesusingMaven2">Getting the Binaries using
Maven 2</h3><p>To use this release in your maven project, the proper dependency
configuration that you should use in your <a shape="rect" class="external-link"
href="http://maven.apache.org/guides/introduction/introducti
on-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="wiki-content maincontent"><h1
id="Camel2.19Release-Camel2.19.0Release(currentlyinprogress)">Camel 2.19.0
Release (currently in progress)</h1><div
style="padding-right:20px;float:left;margin-left:-20px;"><span
class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image
confluence-external-resource"
src="http://camel.apache.org/images/camel-box-small.png";
data-image-src="http://camel.apache.org/images/camel-box-small.png";></span></div><div
style="min-height:200px"> </div><h2
id="Camel2.19Release-NewandNoteworthy">New and Noteworthy</h2><p>Welcome to the
2.19.0 release which approx XXX issues resolved (new features, improvements and
bug fixes such
as...)</p><ul><li>Returning <code>null</code> from <a
shape="rect" href="bean.html">Bean</a> should work similar to
how <code>setBody</code> and <code>transform</code> works
when they set a <code>null</code> body.</li><li>The Camel Spring Boot
starter components
now have their auto configuration depends
on <code>org.apache.camel.springboot.CamelAutoConfiguration</code> which
makes it easier writing unit tests where you can
exclude <code>org.apache.camel.springboot.CamelAutoConfiguration</code> to
turn off Camel Spring Boot auto configuration completely.</li><li>Camel now
supports OWASP dependency check maven plugin</li><li>Camel-Nats component now
supports TLS</li><li>Camel-Nats component now supports explicit flushing (with
timeout) of the connection</li><li>Camel-Metrics component now supports Gauge
type</li><li><a shape="rect" href="file2.html">File consumer</a> now
supports idempotent-changed and idempotent-rename read lock strategies for
clustering. </li><li>Camel Catalog now supports custom runtime providers
that only includes the supported Camel components, languages and data formats
running in that container. For example for Karaf or Spring Boot in the
camel-catalog-provider-karaf and camel-catalog-provider-sprin
gboot.</li><li>The <a shape="rect"
href="https://cwiki.apache.org/confluence/display/WW/bean";>bean</a> component
will when calling a method that returned an instance of
<code>Callable</code> now call that callable to obtain the chained result.
This allows to call Groovy functions/closures etc.</li><li>Failover <a
shape="rect" href="load-balancer.html">Load Balancer</a> with
inheritErrorHandler=false, now allows Camel's <a shape="rect"
href="error-handler.html">Error Handler</a> to react after the load balancer is
exhausted.</li></ul><p>Fixed these issues</p><ul><li>Fixed <a shape="rect"
href="hystrix-eip.html">Hystrix EIP</a> to also execute fallback if execution
was rejected or short-circuited or other reasons from
Hystrix. </li><li>Fixed adding new routes to running CamelContext and if
the new routes would fail to startup, then before these routes would "hang
around". Now only succesful started routes are added.</li><li>Adding or
removing routes that
starts from <a shape="rect" href="undertow.html">Undertow</a> no longer
restart the entire HTTP server</li><li><a shape="rect" href="vm.html">VM</a>
endpoint should prepare exchange with the CamelContext from the consumer and
not from cached endpoint which can be different</li><li>Fixed a bug when
using <a shape="rect" href="rest-dsl.html">Rest DSL</a> with <a
shape="rect" href="servlet.html">SERVLET</a> could cause a java.io.IOException:
Stream closed exception when using <a shape="rect"
href="bean.html">Bean</a> in the route. </li><li>Fixed an issue when
using <code>pipeline</code> in Java DSL not setting up the EIP correctly
which could lead to runtime route not as intended.</li><li>Fixed <a
shape="rect" href="dropbox.html">Dropbox</a> to use <a shape="rect"
href="stream-caching.html">Stream caching</a> to avoid reading entire file into
memory so Camel can process big files</li><li>Fixed Netty douhle buffer release
leak in <a shape="re
ct" href="netty4.html">Netty4</a> and <a shape="rect"
href="netty4-http.html">Netty4 HTTP</a></li></ul><h3
id="Camel2.19Release-New">New <a shape="rect"
href="enterprise-integration-patterns.html">Enterprise Integration
Patterns</a></h3><h3 id="Camel2.19Release-New.1">New <a shape="rect"
href="components.html">Components</a></h3><ul><li>camel-bonita - allow you
to communicate with a remote Bonita engine.</li><li>camel-firebase - allow you
to communicate with Google Firebase Database</li><li>camel-google-pubsub -
allow you communicate with Google Cloud Pub/Sub</li></ul><h3
id="Camel2.19Release-NewDSL">New DSL</h3><h3
id="Camel2.19Release-NewAnnotations">New Annotations</h3><h3
id="Camel2.19Release-New.2">New <a shape="rect" href="data-format.html">Data
Format</a></h3><h3 id="Camel2.19Release-New.3">New <a shape="rect"
href="languages.html">Languages</a></h3><h3 id="Camel2.19Release-New.4">New <a
shape="rect" href="examples.html">Examples</a></h3><h3 id="Camel2.19Release-New
.5">New <a shape="rect" href="tutorials.html">Tutorials</a></h3><h2
id="Camel2.19Release-APIbreaking">API breaking</h2><h2
id="Camel2.19Release-KnownIssues">Known Issues</h2><h2
id="Camel2.19Release-Importantchangestoconsiderwhenupgrading">Important changes
to consider when upgrading</h2><ul><li>Camel now uses Karaf 4.x API and
therefore not possible to run on older Karaf versions</li><li>camel-spring-boot
now don't include prototype scoped beans when auto scanning for RouteBuilder
instances, which is how camel-spring works. You can turn this back using
the includeNonSingletons option.</li></ul><h2
id="Camel2.19Release-GettingtheDistributions">Getting the Distributions</h2><h3
id="Camel2.19Release-BinaryDistributions">Binary Distributions</h3><div
class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1"
rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1"
rowspan="1"
class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>Windows
Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a
shape="rect" class="external-link"
href="http://www.apache.org/dyn/closer.cgi/camel/apache-camel/x.y.x/apache-camel-x.y.x.zip";>apache-camel-x.y.x.zip</a></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect"
class="external-link"
href="http://www.apache.org/dist/camel/apache-camel/x.y.x/apache-camel-x.y.x.zip.asc";>apache-camel-x.y.x.zip.asc</a></p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin
Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a
shape="rect" class="external-link"
href="http://www.apache.org/dyn/closer.cgi/camel/apache-camel/x.y.x/apache-camel-x.y.x.tar.gz";>apache-camel-x.y.x.tar.gz</a></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect"
class="external-link
"
href="http://www.apache.org/dist/camel/apache-camel/x.y.x/apache-camel-x.y.x.tar.gz.asc";>apache-camel-x.y.x.tar.gz.asc</a></p></td></tr></tbody></table></div><div
class="confluence-information-macro
confluence-information-macro-information"><p class="title">The above URLs use
redirection</p><span class="aui-icon aui-icon-small aui-iconfont-info
confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>The above URLs use the Apache
Mirror system to redirect you to a suitable mirror for your download. Some
users have experienced issues with some versions of browsers (e.g. some Safari
browsers). If the download doesn't seem to work for you from the above URL then
try using <a shape="rect" class="external-link"
href="http://www.mozilla.com/en-US/firefox/";
rel="nofollow">FireFox</a></p></div></div><h3
id="Camel2.19Release-SourceDistributions">Source Distributions</h3><div
class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1"
rows
pan="1" class="confluenceTh"><p>Description</p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p>PGP Signature file of
download</p></th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>Source (zip)</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><a shape="rect" class="external-link"
href="http://www.apache.org/dyn/closer.cgi/camel/apache-camel/x.y.x/apache-camel-x.y.x-src.zip";>apache-camel-x.y.x-src.zip</a></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect"
class="external-link"
href="http://www.apache.org/dist/camel/apache-camel/x.y.x/apache-camel-x.y.x-src.zip.asc";>apache-camel-x.y.x-src.zip.asc</a></p></td></tr></tbody></table></div><h3
id="Camel2.19Release-GettingtheBinariesusingMaven2">Getting the Binaries using
Maven 2</h3><p>To use this release in your maven project, the proper dependency
configuration that you should use in your <a shape="rect" cl
ass="external-link"
href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html";>Maven
POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-core</artifactId>
Modified: websites/production/camel/content/jms.html
==============================================================================
--- websites/production/camel/content/jms.html (original)
+++ websites/production/camel/content/jms.html Fri Nov 25 10:21:01 2016
@@ -107,7 +107,7 @@
<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[jms:topic:Stocks.Prices
]]></script>
</div></div><p>You append query options to the URI using the following format:
<strong><code>?option=value&option=value&...</code></strong></p><h3
id="JMS-Notes">Notes</h3><div class="confluence-information-macro
confluence-information-macro-tip"><p class="title">Using ActiveMQ</p><span
class="aui-icon aui-icon-small aui-iconfont-approve
confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>The JMS component reuses Spring
2's <strong><code>JmsTemplate</code></strong> for sending messages. This is not
ideal for use in a non-J2EE container and typically requires some caching in
the JMS provider to avoid <a shape="rect" class="external-link"
href="http://activemq.apache.org/jmstemplate-gotchas.html";>poor
performance</a>.</p><p>If you intend to use <a shape="rect"
class="external-link" href="http://activemq.apache.org/";>Apache ActiveMQ</a> as
your Message Broker - which is a good choice as ActiveMQ rocks <img
class="emoticon emoticon-smile"
src="https://cwiki.apache.org/confluence/s/en_GB/5982/f2b47fb3d636c8bc9fd0b11c0ec6d0ae18646be7.1/_/images/icons/emoticons/smile.png";
data-emoticon-name="smile" alt="(smile)"> , then we recommend that you
either:</p><ul><li><p>Use the <a shape="rect" href="activemq.html">ActiveMQ</a>
component, which is already optimized to use ActiveMQ
efficiently</p></li><li><p>Use the
<strong><code>PoolingConnectionFactory</code></strong> in
ActiveMQ</p></li></ul></div></div><h4
id="JMS-TransactionsandCacheLevels">Transactions and Cache Levels</h4><p><span
class="confluence-anchor-link" id="JMS-transactionCacheLevels"></span><br
clear="none"> If you are consuming messages and using transactions
(<strong><code>transacted=true</code></strong>) then the default cache level
can negatively impact performance. If you are using XA transactions then you
cannot cache as it can cause the XA transaction to not work properly.</p><p>If
you are <em>not</em> using XA, then you should consider caching as it speed
s up performance, such as setting
<strong><code>cacheLevelName=CACHE_CONSUMER</code></strong>. Through Camel
2.7.x, the default setting for <strong><code>cacheLevelName</code></strong> is
<strong><code>CACHE_CONSUMER</code></strong>. You will need to explicitly set
<strong><code>cacheLevelName=CACHE_NONE</code></strong>. In Camel 2.8 onward,
the default setting for <strong><code>cacheLevelName</code></strong> is
<strong><code>CACHE_AUTO</code></strong>. This default auto detects the mode
and sets the cache level accordingly to:</p><ul
class="alternate"><li><p><strong><code>CACHE_CONSUMER</code></strong>
when <strong><code>transacted=false</code></strong></p></li><li><p><strong><code>CACHE_NONE</code></strong>
when <strong><code>transacted=true</code></strong></p></li></ul><p>So you
can say the default setting is conservative. Consider using
<strong><code>cacheLevelName=CACHE_CONSUMER</code></strong> if you are using
non-XA transactions.</p><h4 id="JMS-DurableSubscriptions"
>Durable Subscriptions</h4><p>If you wish to use durable topic subscriptions,
>you need to specify both <strong><code>clientId</code></strong> 
>and <strong><code>durableSubscriptionName</code>. </strong>The value of
>the<strong> <code>clientId</code></strong> must be unique and can only be
>used by a single JMS connection instance in your entire network. You may
>prefer to use <a shape="rect" class="external-link"
>href="http://activemq.apache.org/virtual-destinations.html";>Virtual
>Topics</a> instead to avoid this limitation. More background on durable
>messaging <a shape="rect" class="external-link"
>href="http://activemq.apache.org/how-do-durable-queues-and-topics-work.html";>here</a>.</p><h4
> id="JMS-MessageHeaderMapping">Message Header Mapping</h4><p>When using
>message headers, the JMS specification states that header names must be valid
>Java identifiers. So try to name your headers to be valid Java identifiers.
>One benefit of doing this is that you can then use your headers in
side a JMS Selector (whose SQL92 syntax mandates Java identifier syntax for
headers).</p><p>A simple strategy for mapping header names is used by default.
The strategy is to replace any dots and hyphens in the header name as shown
below and to reverse the replacement when the header name is restored from a
JMS message sent over the wire. What does this mean? No more losing method
names to invoke on a bean component, no more losing the filename header for the
File Component, and so on.</p><p>The current header name strategy for accepting
header names in Camel is:</p><ul class="alternate"><li><p>Dots are replaced by
<strong><code>_DOT_</code></strong> and the replacement is reversed when Camel
consume the message</p></li><li><p>Hyphen is replaced by
<strong><code>_HYPHEN_</code></strong> and the replacement is reversed when
Camel consumes the message</p></li></ul><h3
id="JMS-ConfigurationOptions">Configuration Options</h3><p>You can configure
many different properties on the JMS endpo
int which map to properties on the <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-jms/apidocs/org/apache/camel/component/jms/JmsConfiguration.html";>JMSConfiguration
POJO</a>.</p><div class="confluence-information-macro
confluence-information-macro-note"><p class="title">Mapping to Spring
JMS</p><span class="aui-icon aui-icon-small aui-iconfont-warning
confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>Many of these properties map to
properties on Spring JMS, which Camel uses for sending and receiving messages.
Therefore for more information about these properties consult the Spring
documentation.</p></div></div><p>The options are divided into two tables, the
first one contains the most common options. The second table contains the less
common and more advanced options.</p><h4 id="JMS-CommonOptions">Common
Options</h4><p> </p><div class="confluenceTableSmall"><div
class="table-wrap">
- <table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Option</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Default Value</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>clientId</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Sets the JMS client ID to use.
Note that this value, if specified, must be unique and can only be used by a
single JMS connection instance. It is typically only required for durable topic
subscriptions. You may prefer to use <a shape="rect" class="external-link"
href="http://activemq.apache.org/virtual-destinations.html";>Virtual Topics</a>
instead.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>concurrentConsumers</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>1
</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Specifies
the default number of concurrent consumers.</p><p>From <strong>Camel
2.10.3</strong>: this option can also be used when doing request/reply over
JMS.</p><p>From <strong>Camel 2.16</strong>: there is a new
<strong><code>replyToConcurrentConsumers</code></strong>.</p><p>See the
<strong><code>maxMessagesPerTask</code></strong> option to control dynamic
scaling up/down of threads.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>disableReplyTo</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>When <strong><code>true</code></strong>, a
producer will behave like a <strong><code>InOnly</code></strong> exchange
with the exception that <strong><code>JMSReplyTo</code></strong> header is sent
out and not be suppressed like in the case of
<strong><code>InOnly</code></strong>. Like <strong><cod
e>InOnly</code></strong> the producer will not wait for a reply. A consumer
with this flag will behave like <strong><code>InOnly</code></strong>. This
feature can be used to bridge <strong><code>InOut</code></strong> requests to
another queue so that a route on the other queue will send it´s response
directly back to the original
<strong><code>JMSReplyTo</code></strong>.</p></td></tr><tr><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>durableSubscriptionName</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The durable subscriber name for
specifying durable topic subscriptions. The
<strong><code>clientId</code></strong> option <strong>must</strong> be
configured as well.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>maxConcurrentConsumers</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>1</code></p></td><td
colspan="1" row
span="1" class="confluenceTd"><p>Specifies the maximum number of concurrent
consumers.</p><p>From <strong>Camel 2.10.3</strong>: this option can also be
used when doing request/reply over JMS. <span> </span></p><p><span>From
</span><strong>Camel 2.16</strong><span>: there is a new
<strong><code>replyToMaxConcurrentConsumers</code></strong>. </span></p><p>See
also the <strong><code>maxMessagesPerTask</code></strong> option to control
dynamic scaling up/down of threads.</p><p>The
<strong><code>maxMessagesPerTask</code></strong><span> option <em>must</em> be
set to an integer greater than <strong><code>0</code></strong> for threads
to scale down. Otherwise, the number of threads will remain at
<span><strong><code>maxConcurrentConsumers</code></strong> until
shutdown.</span></span></p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>maxMessagesPerTask</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>-1</code></p></td><td colspan="
1" rowspan="1" class="confluenceTd"><p>The number of messages a task can
receive after which it's terminated. The default,
<strong><code>-1</code></strong>, is unlimited.</p><p>If you use a range for
concurrent consumers
e.g., <strong><code>concurrentConsumers</code></strong> <code><</code>
<strong><code>maxConcurrentConsumers</code></strong> then this option can be
used to set a value to e.g., <strong><code>100</code></strong> to control how
fast the consumers will shrink when less work is required.</p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>preserveMessageQos</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Set to <strong><code>true</code></strong>,
if you want to send message using the QoS settings specified on the message,
instead of the QoS settings on the JMS endpoint. The following headers are
considered:</p>
+ <table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Option</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Default Value</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>clientId</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Sets the JMS client ID to use.
Note that this value, if specified, must be unique and can only be used by a
single JMS connection instance. It is typically only required for durable topic
subscriptions. You may prefer to use <a shape="rect" class="external-link"
href="http://activemq.apache.org/virtual-destinations.html";>Virtual Topics</a>
instead.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>concurrentConsumers</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>1
</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Specifies
the default number of concurrent consumers.</p><p>From <strong>Camel
2.10.3</strong>: this option can also be used when doing request/reply over
JMS.</p><p>From <strong>Camel 2.16</strong>: there is a new
<strong><code>replyToConcurrentConsumers</code></strong>.</p><p>See the
<strong><code>maxMessagesPerTask</code></strong> option to control dynamic
scaling up/down of threads.</p><p>When using ActiveMQ beware that the default
prefetch policy loads 1000 messages per consumer. See <a shape="rect"
class="external-link"
href="http://activemq.apache.org/what-is-the-prefetch-limit-for.html";>What is
the prefetch limit</a> on how to change this.</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>disableReplyTo</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>When
<strong><code>true</code></stron
g>, a producer will behave like a <strong><code>InOnly</code></strong>
exchange with the exception that <strong><code>JMSReplyTo</code></strong>
header is sent out and not be suppressed like in the case of
<strong><code>InOnly</code></strong>. Like <strong><code>InOnly</code></strong>
the producer will not wait for a reply. A consumer with this flag will behave
like <strong><code>InOnly</code></strong>. This feature can be used to bridge
<strong><code>InOut</code></strong> requests to another queue so that a route
on the other queue will send it´s response directly back to the original
<strong><code>JMSReplyTo</code></strong>.</p></td></tr><tr><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>durableSubscriptionName</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The durable subscriber name for
specifying durable topic subscriptions. The <strong><code>clientId</code></s
trong> option <strong>must</strong> be configured as
well.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>maxConcurrentConsumers</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>1</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Specifies the maximum number of
concurrent consumers.</p><p>From <strong>Camel 2.10.3</strong>: this option can
also be used when doing request/reply over JMS.
<span> </span></p><p><span>From </span><strong>Camel 2.16</strong><span>:
there is a new <strong><code>replyToMaxConcurrentConsumers</code></strong>.
</span></p><p>See also the <strong><code>maxMessagesPerTask</code></strong>
option to control dynamic scaling up/down of threads.</p><p>The
<strong><code>maxMessagesPerTask</code></strong><span> option <em>must</em> be
set to an integer greater than <strong><code>0</code></strong> for threads
to scale down. Otherwise, the number of threads will remain at
<span><strong><code>m
axConcurrentConsumers</code></strong> until
shutdown.</span></span></p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>maxMessagesPerTask</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>-1</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>The number of messages a task can receive
after which it's terminated. The default, <strong><code>-1</code></strong>, is
unlimited.</p><p>If you use a range for concurrent consumers
e.g., <strong><code>concurrentConsumers</code></strong> <code><</code>
<strong><code>maxConcurrentConsumers</code></strong> then this option can be
used to set a value to e.g., <strong><code>100</code></strong> to control how
fast the consumers will shrink when less work is required.</p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>preserveMessageQos</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1"
rowspan=
"1" class="confluenceTd"><p>Set to <strong><code>true</code></strong>, if you
want to send message using the QoS settings specified on the message, instead
of the QoS settings on the JMS endpoint. The following headers are
considered:</p>
<ul><li><strong><code>JMSPriority</code></strong></li><li><strong><code>JMSDeliveryMode</code></strong></li><li><strong><code>JMSExpiration</code></strong>.</li></ul><p>You
can provide some or all of them.</p><p>If not provided, Camel will fall back
to use the values from the endpoint instead. So, when using this option, the
headers override the values from the endpoint.</p><p>The
<strong><code>explicitQosEnabled</code></strong> option, by contrast, will only
use options set on the endpoint, and not values from the message
header.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>replyTo</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Provides an
explicit <strong><code>ReplyTo</code></strong> destination, which
overrides any incoming value of
<strong><code>Message.getJMSReplyTo()</code></strong>.</p><p>If you do <a
shape="rect" href="request-reply.html"
>Request Reply</a> over JMS then <strong>make sure</strong> to read the
>section <em>Request-reply over JMS</em> further below for more details, and
>the <strong><code>replyToType</code></strong> option as
>well.</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p><code>replyToConcurrentConsumers</code></p></td><td
>colspan="1" rowspan="1" class="confluenceTd"><p><code>1</code></p></td><td
>colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.16</strong>:
>Specifies the default number of concurrent consumers when doing request/reply
>over JMS.</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p><code>replyToMaxConcurrentConsumers</code></p></td><td
> colspan="1" rowspan="1" class="confluenceTd"><p><code>1</code></p></td><td
>colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.16</strong>:
>Specifies the maximum number of concurrent consumers when doing request/reply
>over JMS.</p><p>See the <strong><code>maxMessagesPerTask</code></st
rong> option to control dynamic scaling up/down of
threads.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>replyToOnTimeoutMaxConcurrentConsumers</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>1</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.17.2</strong>:
Specifies the maximum number of concurrent consumers for continue routing when
timeout occurred when using request/reply over JMS.</p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>replyToOverride</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><strong>Camel 2.15:</strong> Provides an
explicit <strong><code>ReplyTo</code></strong> destination in the JMS
message, which overrides the setting of <strong><code>ReplyTo</code></strong>.
It is useful if you want to forward the message to a remote Queue and receive
the reply
message from the <strong><code>ReplyTo</code></strong>
destination.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>replyToType</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><strong>Camel 2.9:</strong> Allows for
explicitly specifying which kind of strategy to use
for <strong><code>replyTo</code></strong> queues when doing request/reply
over JMS. Possible values are:</p>
<ul><li><strong><code>Temporary</code></strong></li><li><strong><code>Shared</code></strong></li><li><strong><code>Exclusive</code></strong></li></ul><p>By
default Camel will use <strong><code>Temporary</code></strong>
queues.</p><p>However if <strong><code>replyTo</code></strong> has been
configured, then <strong><code>Shared</code></strong> is used by default. This
option allows you to use exclusive queues instead of shared queues.</p><p>For
more details see below, and especially the notes about the implications if
running in a clustered environment, and the fact that
<strong><code>Shared</code></strong> reply queues has lower performance than
its alternatives <strong><code>Temporary</code></strong> and
<strong><code>Exclusive</code></strong>.</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>requestTimeout</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>20000</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd
"><p><strong>Producer only:</strong> The timeout for waiting for a reply when
using the <strong><code>InOut</code></strong> <a shape="rect"
href="exchange-pattern.html">Exchange Pattern</a> (in milliseconds).</p><p>From
<strong>Camel 2.13/2.12.3</strong>: you can include the header
<strong><code>CamelJmsRequestTimeout</code></strong> to override this endpoint
configured timeout value, and thus have per message individual timeout
values.</p><p>See below in section <em>About time to live</em> for more
details. See also
the <strong><code>requestTimeoutCheckerInterval</code></strong>
option.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>selector</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Sets the JMS Selector, which is an SQL 92
predicate that is used to filter messages within the broker. You may have to
encode special characters like '<strong><cod
e>='</code></strong>
as <strong><code>%3D</code></strong>.</p><p>Before<strong> Camel
2.3.0</strong>: this option was not supported
in <strong><code>CamelConsumerTemplate</code></strong>.</p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>timeToLive</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>When sending messages, specifies the
time-to-live of the message (in milliseconds).</p><p>See below in section
<em>About time to live</em> for more details.</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>transacted</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Specifies whether to use
transacted mode for sending/receiving messages using
the <strong><code>InOnly</code></strong> <a shape="rect"
href="exchange-pattern.html">Exchange P
attern</a>.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>testConnectionOnStartup</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.1:</strong>
Specifies whether to test the connection on startup. This ensures that when
Camel starts that all the JMS consumers have a valid connection to the JMS
broker. If a connection cannot be granted then Camel throws an exception on
startup. This ensures that Camel is not started with failed
connections.</p><p>From <strong>Camel 2.8</strong>: also the JMS producers is
tested as well.</p></td></tr></tbody></table>
</div><h4 id="JMS-AdvancedOptions">Advanced Options</h4><div
class="confluenceTableSmall">
![http://camel.apache.org/images/camel-box-small.png"](http://camel.apache.org/images/camel-box-small.png"){kind=link}
![https://cwiki.apache.org/confluence/s/en_GB/5982/f2b47fb3d636c8bc9fd0b11c0ec6d0ae18646be7.1/_/images/icons/emoticons/smile.png"](https://cwiki.apache.org/confluence/s/en_GB/5982/f2b47fb3d636c8bc9fd0b11c0ec6d0ae18646be7.1/_/images/icons/emoticons/smile.png"){kind=link}