Author: buildbot
Date: Sat May 21 14:19:12 2016
New Revision: 988823

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 Sat May 21 14:19:12 2016
@@ -105,7 +105,7 @@
 </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="brush: java; gutter: false; theme: Default" 
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&amp;option=value&amp;...</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>&#160;</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/5982/f2b47fb3d636c8bc9fd0b11c0ec6d0ae18646be7.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>&#160;</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>&#160;</p></td><td colspan="1" 
rowspan="1" 
class="confluenceTd"><p><code>DefaultJmsKeyFormatStrategy</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>&#160;</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>&#160;</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>DefaultJmsKeyFormatStrategy</code></p></td><td 
colspan="1" r
 owspan="1" class="confluenceTd"><p><strong>Camel 2.15.x or older</strong>: See 
option below</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><code>jmsKeyFormatStrategy</code></td><td colspan="1" 
rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" 
class="confluenceTd"><code>DefaultJmsKeyFormatStrategy</code></td><td 
colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.16:</strong> <span 
style="color: rgb(0,0,0);">Pluggable strategy for encoding and decoding JMS 
keys so they can be compliant with the JMS specification. Camel provides two 
implementations out of the box:&#160;</span><code>default</code><span 
style="color: rgb(0,0,0);">&#160;and&#160;</span><code>passthrough</code><span 
style="color: rgb(0,0,0);">. The&#160;</span><code>default</code><span 
style="color: rgb(0,0,0);">&#160;strategy will safely marshal dots and hyphens 
(</span><code>.</code><span style="color: 
rgb(0,0,0);">&#160;and&#160;</span><code>-</code><span style="color: 
 rgb(0,0,0);">). The&#160;</span><code>passthrough</code><span style="color: 
rgb(0,0,0);">&#160;strategy leaves the key as is. Can be used for JMS brokers 
which do not care whether JMS header keys contain illegal characters. You can 
provide your own implementation of 
the</span><code>org.apache.camel.component.jms.JmsKeyFormatStrategy</code><span 
style="color: rgb(0,0,0);">&#160;and refer to it using 
the&#160;</span><code>#</code><span style="color: 
rgb(0,0,0);">&#160;notation.</span></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>transactionCommitStrategy</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>&#160;</p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>&#160;</p></td></tr><tr><td colspan="1" 
rowspan="1" 
class="confluenceTd"><code>DestinationCreationStrategy</code></td><td 
colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspa
 n="1" 
class="confluenceTd"><code>DefaultDestinationCreationStrategy</code></td><td 
colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.15.0</strong>: 
Support to set the custom DestinationCreationStrategy on the SJMS 
Component.</td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><code>messageCreatedStrategy</code></td><td colspan="1" 
rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" 
class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" 
class="confluenceTd"><strong>Camel 2.16:</strong> <span style="line-height: 
1.42857;">To use the given MessageCreatedStrategy which are invoked when Camel 
creates new instances of javax.jms.Message objects when Camel is sending a JMS 
message.</span></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">
+</div></div><p>You append query options to the URI using the following format, 
<code>?option=value&amp;option=value&amp;...</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>&#160;</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/5982/f2b47fb3d636c8bc9fd0b11c0ec6d0ae18646be7.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>&#160;</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>&#160;</p></td><td colspan="1" 
rowspan="1" 
class="confluenceTd"><p><code>DefaultJmsKeyFormatStrategy</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>&#160;</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>&#160;</p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>DefaultJmsKeyFormatStrategy</code></p></td><td 
colspan="1" r
 owspan="1" class="confluenceTd"><p><strong>Camel 2.15.x or older</strong>: See 
option below</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><code>jmsKeyFormatStrategy</code></td><td colspan="1" 
rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" 
class="confluenceTd"><code>DefaultJmsKeyFormatStrategy</code></td><td 
colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.16:</strong> <span 
style="color: rgb(0,0,0);">Pluggable strategy for encoding and decoding JMS 
keys so they can be compliant with the JMS specification. Camel provides two 
implementations out of the box:&#160;</span><code>default</code><span 
style="color: rgb(0,0,0);">&#160;and&#160;</span><code>passthrough</code><span 
style="color: rgb(0,0,0);">. The&#160;</span><code>default</code><span 
style="color: rgb(0,0,0);">&#160;strategy will safely marshal dots and hyphens 
(</span><code>.</code><span style="color: 
rgb(0,0,0);">&#160;and&#160;</span><code>-</code><span style="color: 
 rgb(0,0,0);">). The&#160;</span><code>passthrough</code><span style="color: 
rgb(0,0,0);">&#160;strategy leaves the key as is. Can be used for JMS brokers 
which do not care whether JMS header keys contain illegal characters. You can 
provide your own implementation of 
the</span><code>org.apache.camel.component.jms.JmsKeyFormatStrategy</code><span 
style="color: rgb(0,0,0);">&#160;and refer to it using 
the&#160;</span><code>#</code><span style="color: 
rgb(0,0,0);">&#160;notation.</span></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>transactionCommitStrategy</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>&#160;</p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" 
rowspan="1" class="confluenceTd"><p>&#160;</p></td></tr><tr><td colspan="1" 
rowspan="1" 
class="confluenceTd"><code>DestinationCreationStrategy</code></td><td 
colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspa
 n="1" 
class="confluenceTd"><code>DefaultDestinationCreationStrategy</code></td><td 
colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.15.0</strong>: 
Support to set the custom DestinationCreationStrategy on the SJMS 
Component.</td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><code>messageCreatedStrategy</code></td><td colspan="1" 
rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" 
class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" 
class="confluenceTd"><strong>Camel 2.16:</strong> <span style="line-height: 
1.42857;">To use the given MessageCreatedStrategy which are invoked when Camel 
creates new instances of javax.jms.Message objects when Camel is sending a JMS 
message.</span></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><code>completionPredicate</code></td><td colspan="1" 
rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" 
class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="conflue
 nceTd"><strong>Camel 2.18:</strong> The completion predicate, which causes 
batches to be completed when the predicate evaluates as true. <span 
style="line-height: 1.42857;">The predicate can also be configured using the 
simple language using the string syntax.</span> You may want to set the option 
eagerCheckCompletion to true to let the predicate match the incoming message, 
as otherwise it matches the aggregated message.</td></tr><tr><td colspan="1" 
rowspan="1" class="confluenceTd"><code>eagerCheckCompletion</code></td><td 
colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" 
rowspan="1" class="confluenceTd"><code>false</code></td><td colspan="1" 
rowspan="1" class="confluenceTd"><strong>Camel 2.18:</strong> Use eager 
completion checking which means that the completionPredicate will use the 
incoming Exchange. As opposed to without eager completion checking the 
completionPredicate will use the aggregated 
Exchange.</td></tr></tbody></table></div></div><p>Below is an e
 xample 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="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[SjmsComponent component = new SjmsComponent();
 component.setConnectionFactory(new 
ActiveMQConnectionFactory(&quot;tcp://localhost:61616&quot;));
 getContext().addComponent(&quot;sjms&quot;, component);


Reply via email to