You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by bu...@apache.org on 2014/08/25 09:18:24 UTC
svn commit: r920350 - in /websites/production/camel/content:
cache/main.pageCache sjms.html
Author: buildbot
Date: Mon Aug 25 07:18:23 2014
New Revision: 920350
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/sjms.html
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/sjms.html
==============================================================================
--- websites/production/camel/content/sjms.html (original)
+++ websites/production/camel/content/sjms.html Mon Aug 25 07:18:23 2014
@@ -85,108 +85,40 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2 id="SJMS-SJMSComponent">SJMS Component</h2>
-<p><strong>Available as of Camel 2.11</strong></p>
-
-<p>The Simple JMS Component, or SJMS, is a JMS client for use with Camel that uses well known best practices when it comes to JMS client creation and configuration. SJMS contains a brand new JMS client API written explicitly for Camel eliminating third party messaging implementations keeping it light and resilient. The following features is included:</p>
-
-<ul><li>Standard Queue and Topic Support (Durable & Non-Durable)</li><li>InOnly & InOut MEP Support</li><li>Asynchronous Producer and Consumer Processing</li><li>Internal JMS Transaction Support</li></ul>
-
-
-<p>Additional key features include:</p>
-
-<ul><li>Plugable Connection Resource Management</li><li>Session, Consumer, & Producer Pooling & Caching Management</li><li>Batch Consumers and Producers</li><li>Transacted Batch Consumers & Producers</li><li>Support for Customizable Transaction Commit Strategies (Local JMS Transactions only)</li></ul>
-
-
- <div class="aui-message hint shadowed information-macro">
+<div class="wiki-content maincontent"><h2 id="SJMS-SJMSComponent">SJMS Component</h2><p><strong>Available as of Camel 2.11</strong></p><p>The Simple JMS Component, or SJMS, is a JMS client for use with Camel that uses well known best practices when it comes to JMS client creation and configuration. SJMS contains a brand new JMS client API written explicitly for Camel eliminating third party messaging implementations keeping it light and resilient. The following features is included:</p><ul><li>Standard Queue and Topic Support (Durable & Non-Durable)</li><li>InOnly & InOut MEP Support</li><li>Asynchronous Producer and Consumer Processing</li><li>Internal JMS Transaction Support</li></ul><p>Additional key features include:</p><ul><li>Plugable Connection Resource Management</li><li>Session, Consumer, & Producer Pooling & Caching Management</li><li>Batch Consumers and Producers</li><li>Transacted Batch Consumers & Producers</li><li>Support for Customizable Transactio
n Commit Strategies (Local JMS Transactions only)</li></ul> <div class="aui-message hint shadowed information-macro">
<p class="title">Why the S in SJMS</p>
<span class="aui-icon icon-hint">Icon</span>
<div class="message-content">
-
-<p>S stands for Simple and Standard and Springless. Also camel-jms was already taken. <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)"></p>
+ <p>S stands for Simple and Standard and Springless. Also camel-jms was already taken. <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)"></p>
</div>
</div>
-
-
- <div class="aui-message problem shadowed information-macro">
- <span class="aui-icon icon-problem">Icon</span>
- <div class="message-content">
-
-<p>This is a rather new component in a complex world of JMS messaging. So this component is ongoing development and hardening.<br clear="none">
-The classic <a shape="rect" href="jms.html">JMS</a> component based on Spring JMS has been hardened and battle tested extensively.</p>
- </div>
- </div>
-
-
-<p>Maven users will need to add the following dependency to their <code>pom.xml</code> for this component:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
-<dependency>
+<p> </p><p>Maven users will need to add the following dependency to their <code>pom.xml</code> for this component:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-sjms</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>
]]></script>
-</div></div>
-
-<h4 id="SJMS-URIformat">URI format</h4>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-sjms:[queue:|topic:]destinationName[?options]
+</div></div><h4 id="SJMS-URIformat">URI format</h4><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[sjms:[queue:|topic:]destinationName[?options]
]]></script>
-</div></div>
-
-<p>Where <code>destinationName</code> is a JMS queue or topic name. By default, the <code>destinationName</code> is interpreted as a queue name. For example, to connect to the queue, <code>FOO.BAR</code> use:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-sjms:FOO.BAR
+</div></div><p>Where <code>destinationName</code> is a JMS queue or topic name. By default, the <code>destinationName</code> is interpreted as a queue name. For example, to connect to the queue, <code>FOO.BAR</code> use:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[sjms:FOO.BAR
]]></script>
-</div></div>
-
-<p>You can include the optional <code>queue:</code> prefix, if you prefer:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-sjms:queue:FOO.BAR
+</div></div><p>You can include the optional <code>queue:</code> prefix, if you prefer:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[sjms:queue:FOO.BAR
]]></script>
-</div></div>
-
-<p>To connect to a topic, you <em>must</em> include the <code>topic:</code> prefix. For example, to connect to the topic, <code>Stocks.Prices</code>, use:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-sjms:topic:Stocks.Prices
+</div></div><p>To connect to a topic, you <em>must</em> include the <code>topic:</code> prefix. For example, to connect to the topic, <code>Stocks.Prices</code>, use:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[sjms:topic:Stocks.Prices
]]></script>
-</div></div>
-
-<p>You append query options to the URI using the following format, <code>?option=value&option=value&...</code></p>
-
-<h3 id="SJMS-ComponentOptionsandConfigurations">Component Options and Configurations</h3>
-
-<p>The SJMS Component supports the following configuration options:</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> Required </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>connectionCount</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>1</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The maximum number of connections available to endpoints started under this component </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>connectionFactory</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB-198822978
8/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> A <a shape="rect" class="external-link" href="http://docs.oracle.com/javaee/5/api/javax/jms/ConnectionFactory.html" rel="nofollow">ConnectionFactory</a> is required to enable the SjmsComponent. It can be set directly or set set as part of a ConnectionResource. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>connectionResource</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> A ConnectionResource is an interface that allows for customization and container control of the ConnectionFactory. See <a shape="rect" href="#SJMS-connecti
onresource">Plugable Connection Resource Management</a> for further details. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>headerFilterStrategy</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>DefaultJmsKeyFormatStrategy</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>keyFormatStrategy</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>DefaultJmsKeyFormatStrategy</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>transactionCommitStrategy</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr></tbody></table></div>
-</div>
-
-<p>Below is an example of how to configure the SjmsComponent with its required ConnectionFactory provider. It will create a single connection by default and store it using the components internal pooling APIs to ensure that it is able to service Session creation requests in a thread safe manner.</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-SjmsComponent component = new SjmsComponent();
+</div></div><p>You append query options to the URI using the following format, <code>?option=value&option=value&...</code></p><h3 id="SJMS-ComponentOptionsandConfigurations">Component Options and Configurations</h3><p>The SJMS Component supports the following configuration options:</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>Required</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>connectionCount</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>1</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The maximum number of connect
ions available to endpoints started under this component</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>connectionFactory</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>A <a shape="rect" class="external-link" href="http://docs.oracle.com/javaee/5/api/javax/jms/ConnectionFactory.html" rel="nofollow">ConnectionFactory</a> is required to enable the SjmsComponent. It can be set directly or set set as part of a ConnectionResource.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>connectionResource</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>A ConnectionResource is an interface that allows for customization and container control of the ConnectionFactory. See <a shape="rect" href="#SJMS-connectionresource">Plugable Connection Resource Management</a> for further details.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>headerFilterStrategy</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>DefaultJmsKeyFormatStrategy</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>keyFormatStrategy</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>DefaultJmsKeyFormatStrategy</code></p></td><td co
lspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>transactionCommitStrategy</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr></tbody></table></div></div><p>Below is an example of how to configure the SjmsComponent with its required ConnectionFactory provider. It will create a single connection by default and store it using the components internal pooling APIs to ensure that it is able to service Session creation requests in a thread safe manner.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[SjmsComponent component = new SjmsComponent();
component.setConnectionFactory(new ActiveMQConnectionFactory("tcp://localhost:61616"));
getContext().addComponent("sjms", component);
]]></script>
-</div></div>
-
-<p>For a SjmsComponent that is required to support a durable subscription, you can override the default ConnectionFactoryResource instance and set the <strong>clientId</strong> property.</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-ConnectionFactoryResource connectionResource = new ConnectionFactoryResource();
+</div></div><p>For a SjmsComponent that is required to support a durable subscription, you can override the default ConnectionFactoryResource instance and set the <strong>clientId</strong> property.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[ConnectionFactoryResource connectionResource = new ConnectionFactoryResource();
connectionResource.setConnectionFactory(new ActiveMQConnectionFactory("tcp://localhost:61616"));
connectionResource.setClientId("myclient-id");
@@ -194,96 +126,28 @@ SjmsComponent component = new SjmsCompon
component.setConnectionResource(connectionResource);
component.setMaxConnections(1);
]]></script>
-</div></div>
-
-<h3 id="SJMS-ProducerConfigurationOptions">Producer Configuration Options</h3>
-
-<p>The SjmsProducer Endpoint supports the following properties:</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>acknowledgementMode</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>AUTO_ACKNOWLEDGE</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The JMS acknowledgement name, which is one of: <code>SESSION_TRANSACTED</code>, <code>AUTO_ACKNOWLEDGE</code> or <code>DUPS_OK_ACKNOWLEDGE</code>. <code>CLIENT_ACKNOWLEDGE</code> is not supported at this time. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>consumerCount</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>InOut on
ly.</strong> Defines the number of <a shape="rect" class="external-link" href="http://docs.oracle.com/javaee/5/api/javax/jms/MessageListener.html" rel="nofollow">MessageListener</a> instances that for response consumers. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>exchangePattern</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>InOnly</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Sets the Producers message exchange pattern. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>namedReplyTo</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>InOut only.</strong> Specifies a named reply to destination for responses. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>persistent</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>tr
ue</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Whether a message should be delivered with persistence enabled. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>producerCount</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>1</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Defines the number of <a shape="rect" class="external-link" href="http://docs.oracle.com/javaee/5/api/javax/jms/MessageProducer.html" rel="nofollow">MessageProducer</a> instances. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>responseTimeOut</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>5000</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>InOut only.</strong> Specifies the amount of time an InOut Producer will wait for its response. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>synchronous</code> </
p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Sets whether the Endpoint will use synchronous or asynchronous processing. </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> If the endpoint should use a JMS Session transaction. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>ttl</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>-1</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Disabled by default. Sets the Message time to live header. </p></td></tr></tbody></table></div>
-</div>
-
-<h3 id="SJMS-ProducerUsage">Producer Usage</h3>
-
-<h4 id="SJMS-InOnlyProducer-(Default)">InOnly Producer - (Default)</h4>
-
-<p>The InOnly Producer is the default behavior of the SJMS Producer Endpoint.</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-from("direct:start")
+</div></div><h3 id="SJMS-ProducerConfigurationOptions">Producer Configuration Options</h3><p>The SjmsProducer Endpoint supports the following properties:</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>acknowledgementMode</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>AUTO_ACKNOWLEDGE</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The JMS acknowledgement name, which is one of: <code>SESSION_TRANSACTED</code>, <code>AUTO_ACKNOWLEDGE</code> or <code>DUPS_OK_ACKNOWLEDGE</code>. <code>CLIENT_ACKNOWLEDGE</code> is not supported at this time.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><cod
e>consumerCount</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>InOut only.</strong> Defines the number of <a shape="rect" class="external-link" href="http://docs.oracle.com/javaee/5/api/javax/jms/MessageListener.html" rel="nofollow">MessageListener</a> instances that for response consumers.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>exchangePattern</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>InOnly</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets the Producers message exchange pattern.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>namedReplyTo</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>InOut only.</strong> Specifies a named reply to destination for responses.</p>
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>persistent</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Whether a message should be delivered with persistence enabled.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>producerCount</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>1</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Defines the number of <a shape="rect" class="external-link" href="http://docs.oracle.com/javaee/5/api/javax/jms/MessageProducer.html" rel="nofollow">MessageProducer</a> instances.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>responseTimeOut</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>5000</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>InOut only.</strong> Specifies the amount of time
an InOut Producer will wait for its response.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>synchronous</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets whether the Endpoint will use synchronous or asynchronous processing.</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>If the endpoint should use a JMS Session transaction.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ttl</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>-1</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Disabled by default. Sets the Message time to live header.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><pre>prefil
lPool</pre></td><td colspan="1" rowspan="1" class="confluenceTd"><span>true</span></td><td colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.14:</strong> Whether to prefill the producer connection pool on startup, or create connections lazy when needed.</td></tr></tbody></table></div></div><h3 id="SJMS-ProducerUsage">Producer Usage</h3><h4 id="SJMS-InOnlyProducer-(Default)">InOnly Producer - (Default)</h4><p>The InOnly Producer is the default behavior of the SJMS Producer Endpoint.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[from("direct:start")
.to("sjms:queue:bar");
]]></script>
-</div></div>
-
-<h4 id="SJMS-InOutProducer">InOut Producer</h4>
-
-<p>To enable InOut behavior append the <code>exchangePattern</code> attribute to the URI. By default it will use a dedicated TemporaryQueue for each consumer.</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-from("direct:start")
+</div></div><h4 id="SJMS-InOutProducer">InOut Producer</h4><p>To enable InOut behavior append the <code>exchangePattern</code> attribute to the URI. By default it will use a dedicated TemporaryQueue for each consumer.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[from("direct:start")
.to("sjms:queue:bar?exchangePattern=InOut");
]]></script>
-</div></div>
-
-<p>You can specify a <code>namedReplyTo</code> though which can provide a better monitor point.</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-from("direct:start")
+</div></div><p>You can specify a <code>namedReplyTo</code> though which can provide a better monitor point.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[from("direct:start")
.to("sjms:queue:bar?exchangePattern=InOut&namedReplyTo=my.reply.to.queue");
]]></script>
-</div></div>
-
-<h3 id="SJMS-ConsumersConfigurationOptions">Consumers Configuration Options</h3>
-
-<p>The SjmsConsumer Endpoint supports the following properties:</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>acknowledgementMode</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>AUTO_ACKNOWLEDGE</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The JMS acknowledgement name, which is one of: <code>TRANSACTED</code>, <code>AUTO_ACKNOWLEDGE</code> or <code>DUPS_OK_ACKNOWLEDGE</code>. <code>CLIENT_ACKNOWLEDGE</code> is not supported at this time. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>consumerCount</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>1</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Defines the number of <a
shape="rect" class="external-link" href="http://docs.oracle.com/javaee/5/api/javax/jms/MessageListener.html" rel="nofollow">MessageListener</a> instances. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>durableSubscriptionId</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Required for a durable subscriptions. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>exchangePattern</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>InOnly</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Sets the Consumers message exchange pattern. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>messageSelector</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 message selecto
r. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>synchronous</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Sets whether the Endpoint will use synchronous or asynchronous processing. </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> If the endpoint should use a JMS Session transaction. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>transactionBatchCount</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 exchanges to process before committing a local JMS transaction. The <code>transacted</code> property must also be set to true or
this property will be ignored. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>transactionBatchTimeout</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>5000</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The amount of time a the transaction will stay open between messages before committing what has already been consumed. Minimum value is 1000ms. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>ttl</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>-1</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Disabled by default. Sets the Message time to live header. </p></td></tr></tbody></table></div>
-</div>
-
-<h3 id="SJMS-ConsumerUsage">Consumer Usage</h3>
-
-<h4 id="SJMS-InOnlyConsumer-(Default)">InOnly Consumer - (Default)</h4>
-
-<p>The InOnly Consumer is the default Exchange behavior of the SJMS Consumer Endpoint.</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-from("sjms:queue:bar")
+</div></div><h3 id="SJMS-ConsumersConfigurationOptions">Consumers Configuration Options</h3><p>The SjmsConsumer Endpoint supports the following properties:</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>acknowledgementMode</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>AUTO_ACKNOWLEDGE</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The JMS acknowledgement name, which is one of: <code>TRANSACTED</code>, <code>AUTO_ACKNOWLEDGE</code> or <code>DUPS_OK_ACKNOWLEDGE</code>. <code>CLIENT_ACKNOWLEDGE</code> is not supported at this time.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>cons
umerCount</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>1</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Defines the number of <a shape="rect" class="external-link" href="http://docs.oracle.com/javaee/5/api/javax/jms/MessageListener.html" rel="nofollow">MessageListener</a> instances.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>durableSubscriptionId</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Required for a durable subscriptions.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>exchangePattern</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>InOnly</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets the Consumers message exchange pattern.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>messageSelector</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 message selector.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>synchronous</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets whether the Endpoint will use synchronous or asynchronous processing.</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>If the endpoint should use a JMS Session transaction.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>transactionBatchCount</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 exchanges to process before committing a local JMS transaction. The <code>transacted</code> property must also be set to true or this property will be ignored.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>transactionBatchTimeout</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>5000</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The amount of time a the transaction will stay open between messages before committing what has already been consumed. Minimum value is 1000ms.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ttl</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>-1</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Disabled by default. Sets the Message time to live header.</p></td></tr></tbody></table></div></div><h3 id="SJMS-ConsumerUsage">Consumer Usage</h3><h4 id="SJMS-InOnlyConsumer-(Default)">InOnly Consumer - (Default)</h4
><p>The InOnly Consumer is the default Exchange behavior of the SJMS Consumer Endpoint.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[from("sjms:queue:bar")
.to("mock:result");
]]></script>
-</div></div>
-
-<h4 id="SJMS-InOutConsumer">InOut Consumer</h4>
-
-<p>To enable InOut behavior append the <code>exchangePattern</code> attribute to the URI.</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-from("sjms:queue:in.out.test?exchangePattern=InOut")
+</div></div><h4 id="SJMS-InOutConsumer">InOut Consumer</h4><p>To enable InOut behavior append the <code>exchangePattern</code> attribute to the URI.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[from("sjms:queue:in.out.test?exchangePattern=InOut")
.transform(constant("Bye Camel"));
]]></script>
-</div></div>
-
-<h3 id="SJMS-AdvancedUsageNotes">Advanced Usage Notes</h3>
-
-<h4 id="SJMS-PlugableConnectionResourceManagementconnectionresource">Plugable Connection Resource Management <span class="confluence-anchor-link" id="SJMS-connectionresource"></span></h4>
-
-<p>SJMS provides JMS <a shape="rect" class="external-link" href="http://docs.oracle.com/javaee/5/api/javax/jms/Connection.html" rel="nofollow">Connection</a> resource management through built-in connection pooling. This eliminates the need to depend on third party API pooling logic. However there may be times that you are required to use an external Connection resource manager such as those provided by J2EE or OSGi containers. For this SJMS provides an interface that can be used to override the internal SJMS Connection pooling capabilities. This is accomplished through the <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/camel/trunk/components/camel-sjms/src/main/java/org/apache/camel/component/sjms/jms/ConnectionResource.java">ConnectionResource</a> interface. </p>
-
-<p>The <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/camel/trunk/components/camel-sjms/src/main/java/org/apache/camel/component/sjms/jms/ConnectionResource.java">ConnectionResource</a> provides methods for borrowing and returning Connections as needed is the contract used to provide <a shape="rect" class="external-link" href="http://docs.oracle.com/javaee/5/api/javax/jms/Connection.html" rel="nofollow">Connection</a> pools to the SJMS component. A user should use when it is necessary to integrate SJMS with an external connection pooling manager.</p>
-
-<p>It is recommended though that for standard <a shape="rect" class="external-link" href="http://docs.oracle.com/javaee/5/api/javax/jms/ConnectionFactory.html" rel="nofollow">ConnectionFactory</a> providers you use the <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/camel/trunk/components/camel-sjms/src/test/java/org/apache/camel/component/sjms/it/ConnectionResourceIT.java">ConnectionFactoryResource</a> implementation that is provided with SJMS as-is or extend as it is optimized for this component.</p>
-
-<p>Below is an example of using the pluggable ConnectionResource with the ActiveMQ PooledConnectionFactory:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-public class AMQConnectionResource implements ConnectionResource {
+</div></div><h3 id="SJMS-AdvancedUsageNotes">Advanced Usage Notes</h3><h4 id="SJMS-PlugableConnectionResourceManagementconnectionresource">Plugable Connection Resource Management <span class="confluence-anchor-link" id="SJMS-connectionresource"></span></h4><p>SJMS provides JMS <a shape="rect" class="external-link" href="http://docs.oracle.com/javaee/5/api/javax/jms/Connection.html" rel="nofollow">Connection</a> resource management through built-in connection pooling. This eliminates the need to depend on third party API pooling logic. However there may be times that you are required to use an external Connection resource manager such as those provided by J2EE or OSGi containers. For this SJMS provides an interface that can be used to override the internal SJMS Connection pooling capabilities. This is accomplished through the <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/camel/trunk/components/camel-sjms/src/main/java/org/apache/camel/component/sjms/jms
/ConnectionResource.java">ConnectionResource</a> interface.</p><p>The <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/camel/trunk/components/camel-sjms/src/main/java/org/apache/camel/component/sjms/jms/ConnectionResource.java">ConnectionResource</a> provides methods for borrowing and returning Connections as needed is the contract used to provide <a shape="rect" class="external-link" href="http://docs.oracle.com/javaee/5/api/javax/jms/Connection.html" rel="nofollow">Connection</a> pools to the SJMS component. A user should use when it is necessary to integrate SJMS with an external connection pooling manager.</p><p>It is recommended though that for standard <a shape="rect" class="external-link" href="http://docs.oracle.com/javaee/5/api/javax/jms/ConnectionFactory.html" rel="nofollow">ConnectionFactory</a> providers you use the <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/camel/trunk/components/camel-sjms/src/test/java/org/
apache/camel/component/sjms/it/ConnectionResourceIT.java">ConnectionFactoryResource</a> implementation that is provided with SJMS as-is or extend as it is optimized for this component.</p><p>Below is an example of using the pluggable ConnectionResource with the ActiveMQ PooledConnectionFactory:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[public class AMQConnectionResource implements ConnectionResource {
private PooledConnectionFactory pcf;
public AMQConnectionResource(String connectString, int maxConnections) {
@@ -317,140 +181,43 @@ public class AMQConnectionResource imple
}
}
]]></script>
-</div></div>
-
-<p>Then pass in the ConnectionResource to the SjmsComponent:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-CamelContext camelContext = new DefaultCamelContext();
+</div></div><p>Then pass in the ConnectionResource to the SjmsComponent:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[CamelContext camelContext = new DefaultCamelContext();
AMQConnectionResource pool = new AMQConnectionResource("tcp://localhost:33333", 1);
SjmsComponent component = new SjmsComponent();
component.setConnectionResource(pool);
camelContext.addComponent("sjms", component);
]]></script>
-</div></div>
-
-<p>To see the full example of its usage please refer to the <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/camel/trunk/components/camel-sjms/src/test/java/org/apache/camel/component/sjms/it/ConnectionResourceIT.java">ConnectionResourceIT</a>.</p>
-
-<h4 id="SJMS-Session,Consumer,&ProducerPooling&CachingManagement">Session, Consumer, & Producer Pooling & Caching Management</h4>
-
-<p>Coming soon ...</p>
-
-<h4 id="SJMS-BatchMessageSupport">Batch Message Support</h4>
-
-<p>The SjmsProducer supports publishing a collection of messages by creating an Exchange that encapsulates a List. This SjmsProducer will take then iterate through the contents of the List and publish each message individually.</p>
-
-<p>If when producing a batch of messages there is the need to set headers that are unique to each message you can use the SJMS <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/camel/trunk/components/camel-sjms/src/main/java/org/apache/camel/component/sjms/BatchMessage.java">BatchMessage</a> class. When the SjmsProducer encounters a BatchMessage List it will iterate each BatchMessage and publish the included payload and headers.</p>
-
-<p>Below is an example of using the BatchMessage class. First we create a List of BatchMessages:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-List<BatchMessage<String>> messages = new ArrayList<BatchMessage<String>>();
+</div></div><p>To see the full example of its usage please refer to the <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/camel/trunk/components/camel-sjms/src/test/java/org/apache/camel/component/sjms/it/ConnectionResourceIT.java">ConnectionResourceIT</a>.</p><h4 id="SJMS-Session,Consumer,&ProducerPooling&CachingManagement">Session, Consumer, & Producer Pooling & Caching Management</h4><p>Coming soon ...</p><h4 id="SJMS-BatchMessageSupport">Batch Message Support</h4><p>The SjmsProducer supports publishing a collection of messages by creating an Exchange that encapsulates a List. This SjmsProducer will take then iterate through the contents of the List and publish each message individually.</p><p>If when producing a batch of messages there is the need to set headers that are unique to each message you can use the SJMS <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/camel/trunk/components/camel-sjms/src/main/java
/org/apache/camel/component/sjms/BatchMessage.java">BatchMessage</a> class. When the SjmsProducer encounters a BatchMessage List it will iterate each BatchMessage and publish the included payload and headers.</p><p>Below is an example of using the BatchMessage class. First we create a List of BatchMessages:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[List<BatchMessage<String>> messages = new ArrayList<BatchMessage<String>>();
for (int i = 1; i <= messageCount; i++) {
String body = "Hello World " + i;
BatchMessage<String> message = new BatchMessage<String>(body, null);
messages.add(message);
}
]]></script>
-</div></div>
-
-<p>Then publish the List:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-template.sendBody("sjms:queue:batch.queue", messages);
+</div></div><p>Then publish the List:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[template.sendBody("sjms:queue:batch.queue", messages);
]]></script>
-</div></div>
-
-<h4 id="SJMS-CustomizableTransactionCommitStrategies(LocalJMSTransactionsonly)">Customizable Transaction Commit Strategies (Local JMS Transactions only)</h4>
-
-<p>SJMS provides a developer the means to create a custom and plugable transaction strategy through the use of the <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/camel/trunk/components/camel-sjms/src/main/java/org/apache/camel/component/sjms/TransactionCommitStrategy.java">TransactionCommitStrategy</a> interface. This allows a user to define a unique set of circumstances that the <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/camel/trunk/components/camel-sjms/src/main/java/org/apache/camel/component/sjms/tx/SessionTransactionSynchronization.java">SessionTransactionSynchronization</a> will use to determine when to commit the Session. An example of its use is the <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/camel/trunk/components/camel-sjms/src/main/java/org/apache/camel/component/sjms/tx/BatchTransactionCommitStrategy.java">BatchTransactionCommitStrategy</a> which is detailed further in the ne
xt section.</p>
-
-<h4 id="SJMS-TransactedBatchConsumers&Producers">Transacted Batch Consumers & Producers</h4>
-
-<p>The SjmsComponent has been designed to support the batching of local JMS transactions on both the Producer and Consumer endpoints. How they are handled on each is very different though.</p>
-
-<p>The SjmsConsumer endpoint is a straitforward implementation that will process X messages before committing them with the associated Session. To enable batched transaction on the consumer first enable transactions by setting the <code>transacted</code> parameter to true and then adding the <code>transactionBatchCount</code> and setting it to any value that is greater than 0. For example the following configuration will commit the Session every 10 messages:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-sjms:queue:transacted.batch.consumer?transacted=true&transactionBatchCount=10
+</div></div><h4 id="SJMS-CustomizableTransactionCommitStrategies(LocalJMSTransactionsonly)">Customizable Transaction Commit Strategies (Local JMS Transactions only)</h4><p>SJMS provides a developer the means to create a custom and plugable transaction strategy through the use of the <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/camel/trunk/components/camel-sjms/src/main/java/org/apache/camel/component/sjms/TransactionCommitStrategy.java">TransactionCommitStrategy</a> interface. This allows a user to define a unique set of circumstances that the <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/camel/trunk/components/camel-sjms/src/main/java/org/apache/camel/component/sjms/tx/SessionTransactionSynchronization.java">SessionTransactionSynchronization</a> will use to determine when to commit the Session. An example of its use is the <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/camel/trunk/component
s/camel-sjms/src/main/java/org/apache/camel/component/sjms/tx/BatchTransactionCommitStrategy.java">BatchTransactionCommitStrategy</a> which is detailed further in the next section.</p><h4 id="SJMS-TransactedBatchConsumers&Producers">Transacted Batch Consumers & Producers</h4><p>The SjmsComponent has been designed to support the batching of local JMS transactions on both the Producer and Consumer endpoints. How they are handled on each is very different though.</p><p>The SjmsConsumer endpoint is a straitforward implementation that will process X messages before committing them with the associated Session. To enable batched transaction on the consumer first enable transactions by setting the <code>transacted</code> parameter to true and then adding the <code>transactionBatchCount</code> and setting it to any value that is greater than 0. For example the following configuration will commit the Session every 10 messages:</p><div class="code panel pdl" style="border-width: 1px;">
<div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[sjms:queue:transacted.batch.consumer?transacted=true&transactionBatchCount=10
]]></script>
-</div></div>
-
-<p>If an exception occurs during the processing of a batch on the consumer endpoint, the Session rollback is invoked causing the messages to be redelivered to the next available consumer. The counter is also reset to 0 for the BatchTransactionCommitStrategy for the associated Session as well. It is the responsibility of the user to ensure they put hooks in their processors of batch messages to watch for messages with the JMSRedelivered header set to true. This is the indicator that messages were rolled back at some point and that a verification of a successful processing should occur.</p>
-
-<p>A transacted batch consumer also carries with it an instance of an internal timer that waits a default amount of time (5000ms) between messages before committing the open transactions on the Session. The default value of 5000ms (minimum of 1000ms) should be adequate for most use-cases but if further tuning is necessary simply set the <code>transactionBatchTimeout</code> parameter.</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-sjms:queue:transacted.batch.consumer?transacted=true&transactionBatchCount=10&transactionBatchTimeout=2000
+</div></div><p>If an exception occurs during the processing of a batch on the consumer endpoint, the Session rollback is invoked causing the messages to be redelivered to the next available consumer. The counter is also reset to 0 for the BatchTransactionCommitStrategy for the associated Session as well. It is the responsibility of the user to ensure they put hooks in their processors of batch messages to watch for messages with the JMSRedelivered header set to true. This is the indicator that messages were rolled back at some point and that a verification of a successful processing should occur.</p><p>A transacted batch consumer also carries with it an instance of an internal timer that waits a default amount of time (5000ms) between messages before committing the open transactions on the Session. The default value of 5000ms (minimum of 1000ms) should be adequate for most use-cases but if further tuning is necessary simply set the <code>transactionBatchTimeout</code> parameter.</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[sjms:queue:transacted.batch.consumer?transacted=true&transactionBatchCount=10&transactionBatchTimeout=2000
]]></script>
-</div></div>
-
-<p>The minimal value that will be accepted is 1000ms as the amount of context switching may cause unnecessary performance impacts without gaining benefit.</p>
-
-<p>The producer endpoint is handled much differently though. With the producer after each message is delivered to its destination the Exchange is closed and there is no longer a reference to that message. To make a available all the messages available for redelivery you simply enable transactions on a Producer Endpoint that is publishing BatchMessages. The transaction will commit at the conclusion of the exchange which includes all messages in the batch list. Nothing additional need be configured. For example:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-List<BatchMessage<String>> messages = new ArrayList<BatchMessage<String>>();
+</div></div><p>The minimal value that will be accepted is 1000ms as the amount of context switching may cause unnecessary performance impacts without gaining benefit.</p><p>The producer endpoint is handled much differently though. With the producer after each message is delivered to its destination the Exchange is closed and there is no longer a reference to that message. To make a available all the messages available for redelivery you simply enable transactions on a Producer Endpoint that is publishing BatchMessages. The transaction will commit at the conclusion of the exchange which includes all messages in the batch list. Nothing additional need be configured. For example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[List<BatchMessage<String>> messages = new ArrayList<BatchMessage<String>>();
for (int i = 1; i <= messageCount; i++) {
String body = "Hello World " + i;
BatchMessage<String> message = new BatchMessage<String>(body, null);
messages.add(message);
}
]]></script>
-</div></div>
-
-<p>Now publish the List with transactions enabled:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-template.sendBody("sjms:queue:batch.queue?transacted=true", messages);
+</div></div><p>Now publish the List with transactions enabled:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[template.sendBody("sjms:queue:batch.queue?transacted=true", messages);
]]></script>
-</div></div>
-
-<h3 id="SJMS-AdditionalNotes">Additional Notes</h3>
-
-<h4 id="SJMS-MessageHeaderFormat">Message Header Format</h4>
-
-<p>The SJMS Component uses the same header format strategy that is used in the Camel JMS Component. This plugable strategy ensures that messages sent over the wire conform to the JMS Message spec.</p>
-
-<p>For the exchange.in.header the following rules apply for the header keys:</p>
-
-<p>Keys starting with JMS or JMSX are reserved.<br clear="none">
-exchange.in.headers keys must be literals and all be valid Java identifiers (do not use dots in the key name).<br clear="none">
-Camel replaces dots & hyphens and the reverse when when consuming JMS messages:</p>
-<ul><li>is replaced by <em>DOT</em> and the reverse replacement when Camel consumes the message.</li><li>is replaced by <em>HYPHEN</em> and the reverse replacement when Camel consumes the message.<br clear="none">
-See also the option jmsKeyFormatStrategy, which allows use of your own custom strategy for formatting keys.</li></ul>
-
-
-<p>For the exchange.in.header, the following rules apply for the header values:</p>
-
-<h4 id="SJMS-MessageContent">Message Content</h4>
-
-<p>To deliver content over the wire we must ensure that the body of the message that is being delivered adheres to the JMS Message Specification. Therefore, all that are produced must either be primitives or their counter objects (such as Integer, Long, Character). The types, String, CharSequence, Date, BigDecimal and BigInteger are all converted to their toString() representation. All other types are dropped.</p>
-
-<h4 id="SJMS-Clustering">Clustering</h4>
-
-<p>When using InOut with SJMS in a clustered environment you must either use TemporaryQueue destinations or use a unique named reply to destination per InOut producer endpoint. Message correlation is handled by the endpoint, not with message selectors at the broker. The InOut Producer Endpoint uses Java Concurrency Exchangers cached by the Message JMSCorrelationID. This provides a nice performance increase while reducing the overhead on the broker since all the messages are consumed from the destination in the order they are produced by the interested consumer.</p>
-
-<p>Currently the only correlation strategy is to use the JMSCorrelationId. The InOut Consumer uses this strategy as well ensuring that all responses messages to the included JMSReplyTo destination also have the JMSCorrelationId copied from the request as well.</p>
-
-<h3 id="SJMS-TransactionSupporttransactions">Transaction Support <span class="confluence-anchor-link" id="SJMS-transactions"></span></h3>
-
-<p>SJMS currently only supports the use of internal JMS Transactions. There is no support for the Camel Transaction Processor or the Java Transaction API (JTA).</p>
-
-<h4 id="SJMS-DoesSpringlessMeanICan'tUseSpring?">Does Springless Mean I Can't Use Spring?</h4>
-
-<p>Not at all. Below is an example of the SJMS component using the Spring DSL:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-<route
+</div></div><h3 id="SJMS-AdditionalNotes">Additional Notes</h3><h4 id="SJMS-MessageHeaderFormat">Message Header Format</h4><p>The SJMS Component uses the same header format strategy that is used in the Camel JMS Component. This plugable strategy ensures that messages sent over the wire conform to the JMS Message spec.</p><p>For the exchange.in.header the following rules apply for the header keys:</p><p>Keys starting with JMS or JMSX are reserved.<br clear="none"> exchange.in.headers keys must be literals and all be valid Java identifiers (do not use dots in the key name).<br clear="none"> Camel replaces dots & hyphens and the reverse when when consuming JMS messages:</p><ul><li>is replaced by <em>DOT</em> and the reverse replacement when Camel consumes the message.</li><li>is replaced by <em>HYPHEN</em> and the reverse replacement when Camel consumes the message.<br clear="none"> See also the option jmsKeyFormatStrategy, which allows use of your own custom strategy for formattin
g keys.</li></ul><p>For the exchange.in.header, the following rules apply for the header values:</p><h4 id="SJMS-MessageContent">Message Content</h4><p>To deliver content over the wire we must ensure that the body of the message that is being delivered adheres to the JMS Message Specification. Therefore, all that are produced must either be primitives or their counter objects (such as Integer, Long, Character). The types, String, CharSequence, Date, BigDecimal and BigInteger are all converted to their toString() representation. All other types are dropped.</p><h4 id="SJMS-Clustering">Clustering</h4><p>When using InOut with SJMS in a clustered environment you must either use TemporaryQueue destinations or use a unique named reply to destination per InOut producer endpoint. Message correlation is handled by the endpoint, not with message selectors at the broker. The InOut Producer Endpoint uses Java Concurrency Exchangers cached by the Message JMSCorrelationID. This provides a nice pe
rformance increase while reducing the overhead on the broker since all the messages are consumed from the destination in the order they are produced by the interested consumer.</p><p>Currently the only correlation strategy is to use the JMSCorrelationId. The InOut Consumer uses this strategy as well ensuring that all responses messages to the included JMSReplyTo destination also have the JMSCorrelationId copied from the request as well.</p><h3 id="SJMS-TransactionSupporttransactions">Transaction Support <span class="confluence-anchor-link" id="SJMS-transactions"></span></h3><p>SJMS currently only supports the use of internal JMS Transactions. There is no support for the Camel Transaction Processor or the Java Transaction API (JTA).</p><h4 id="SJMS-DoesSpringlessMeanICan'tUseSpring?">Does Springless Mean I Can't Use Spring?</h4><p>Not at all. Below is an example of the SJMS component using the Spring DSL:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeConte
nt panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[<route
id="inout.named.reply.to.producer.route">
<from
uri="direct:invoke.named.reply.to.queue" />
@@ -458,9 +225,7 @@ See also the option jmsKeyFormatStrategy
uri="sjms:queue:named.reply.to.queue?namedReplyTo=my.response.queue&amp;exchangePattern=InOut" />
</route>
]]></script>
-</div></div>
-
-<p>Springless refers to moving away from the dependency on the Spring JMS API. A new JMS client API is being developed from the ground up to power SJMS.</p></div>
+</div></div><p>Springless refers to moving away from the dependency on the Spring JMS API. A new JMS client API is being developed from the ground up to power SJMS.</p></div>
</td>
<td valign="top">
<div class="navigation">