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 2017/06/15 16:25:46 UTC
svn commit: r1014092 [11/14] - in /websites/production/camel/content: ./
2008/04/08/ 2009/01/19/ 2009/10/26/ 2012/01/17/ 2012/03/01/ 2017/06/
2017/06/15/ cache/
Modified: websites/production/camel/content/sjms-batch.html
==============================================================================
--- websites/production/camel/content/sjms-batch.html (original)
+++ websites/production/camel/content/sjms-batch.html Thu Jun 15 16:25:44 2017
@@ -100,7 +100,7 @@
]]></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="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[sjms:queue:FOO.BAR]]></script>
-</div></div><p>Topic consumption is not supported, as there is no advantage to using batch consumption within that context. Topic messages are usually non-persistent, and loss is acceptable. If consumed within a transaction that fails, a topic message will likely not be redelivered by the broker. A plain <a shape="rect" href="sjms.html">SJMS</a> consumer endpoint can be used in conjunction with a regular non-persistence backed <a shape="rect" href="aggregator2.html">aggregator</a> in this scenario.</p><h3 id="SJMSBatch-ComponentOptionsandConfigurations">Component Options and Configurations</h3><p>The SJMS Batch 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 colsp
an="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>aggregationStrategy</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><code>null</code></code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>A reference to an <code>AggregationStrategy</code> in the Camel registry (e.g. <code>#myAggregationStrategy</code>)</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code><code>completionSize</code></code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>200<br clear="none"></code></p></td><td colspan="1" row
span="1" class="confluenceTd"><p>The size of the batch to aggregate.</p><p>Care should be taken to ensure that this is not larger than the JMS consumer's prefetch buffer, or the maximum page size for a queue on the broker; either of these could cause the consumer to hang if no timeout is used.</p><p>A value of 0 or less indicates that <code>completionTimeout</code> only should be used.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>completionTimeout</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>500</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The maximum time to wait from the receipt of the first message before emitting the Exchange.</p><p>A value of 0 or less indicates that <code style="line-height: 1.42857;">completionSize</code> only should be used.</p><p>Notice you cannot use both completion timeout and completion interval at the same ti
me, only one can be configured.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><code>completionTimeout</code></td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.17:</strong> The completion interval in millis, which causes batches to be completed in a scheduled fixed rate every interval. The batch may be empty if the timeout triggered and there was no messages in the batch. Notice you cannot use both completion timeout and completion interval at the same time, only one can be configured.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><code>sendEmptyMessageWhenIdle</code></td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd"><code>false</code></td><td colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.17:</strong> If using completion timeout or int
erval, then the batch may be empty if the timeout triggered and there was no messages in the batch. If this option is true and the batch is empty then an empty message is added to the batch so an empty message is routed.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>pollDuration</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>1000</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The maximum length of a call to <code>MessageConsumer.receive()</code>. The time remaining before timeout takes precedence within a batch.</p><p>This value is effectively the poll time between batches.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><code>timeoutCheckerExecutorService</code></td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluence
Td"><strong>Camel 2.17:</strong> If using the completionInterval option a background thread is created to trigger the completion interval. Set this option to provide a custom thread pool to be used rather than creating a new thread for every consumer.</td></tr></tbody></table></div></div>
+</div></div><p>Topic consumption is not supported, as there is no advantage to using batch consumption within that context. Topic messages are usually non-persistent, and loss is acceptable. If consumed within a transaction that fails, a topic message will likely not be redelivered by the broker. A plain <a shape="rect" href="sjms.html">SJMS</a> consumer endpoint can be used in conjunction with a regular non-persistence backed <a shape="rect" href="aggregator2.html">aggregator</a> in this scenario.</p><h3 id="SJMSBatch-ComponentOptionsandConfigurations">Component Options and Configurations</h3><p>The SJMS Batch 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 colsp
an="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>aggregationStrategy</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/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code><code>null</code></code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>A reference to an <code>AggregationStrategy</code> in the Camel registry (e.g. <code>#myAggregationStrategy</code>)</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code><code>completionSize</code></code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>200<br clear="none"></code></p></td><td colspan="1" row
span="1" class="confluenceTd"><p>The size of the batch to aggregate.</p><p>Care should be taken to ensure that this is not larger than the JMS consumer's prefetch buffer, or the maximum page size for a queue on the broker; either of these could cause the consumer to hang if no timeout is used.</p><p>A value of 0 or less indicates that <code>completionTimeout</code> only should be used.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>completionTimeout</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>500</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The maximum time to wait from the receipt of the first message before emitting the Exchange.</p><p>A value of 0 or less indicates that <code style="line-height: 1.42857;">completionSize</code> only should be used.</p><p>Notice you cannot use both completion timeout and completion interval at the same ti
me, only one can be configured.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><code>completionTimeout</code></td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.17:</strong> The completion interval in millis, which causes batches to be completed in a scheduled fixed rate every interval. The batch may be empty if the timeout triggered and there was no messages in the batch. Notice you cannot use both completion timeout and completion interval at the same time, only one can be configured.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><code>sendEmptyMessageWhenIdle</code></td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd"><code>false</code></td><td colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.17:</strong> If using completion timeout or int
erval, then the batch may be empty if the timeout triggered and there was no messages in the batch. If this option is true and the batch is empty then an empty message is added to the batch so an empty message is routed.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>pollDuration</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>1000</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The maximum length of a call to <code>MessageConsumer.receive()</code>. The time remaining before timeout takes precedence within a batch.</p><p>This value is effectively the poll time between batches.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><code>timeoutCheckerExecutorService</code></td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluence
Td"><strong>Camel 2.17:</strong> If using the completionInterval option a background thread is created to trigger the completion interval. Set this option to provide a custom thread pool to be used rather than creating a new thread for every consumer.</td></tr></tbody></table></div></div>
<p>The <code>completionSize</code> endpoint attribute is used in conjunction with <code>completionTimeout</code>, where the first condition to be met will cause the aggregated <code>Exchange</code> to be emitted down the route.</p><p> </p></div>
Modified: websites/production/camel/content/sjms.html
==============================================================================
--- websites/production/camel/content/sjms.html (original)
+++ websites/production/camel/content/sjms.html Thu Jun 15 16:25:44 2017
@@ -85,7 +85,7 @@
<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 Transactio
n Commit Strategies (Local JMS Transactions only)</li></ul><div class="confluence-information-macro confluence-information-macro-information"><p class="title">Why the S in SJMS</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><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/5982/f2b47fb3d636c8bc9fd0b11c0ec6d0ae18646be7.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)"></p></div></div><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">
+<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="confluence-information-macro confluence-information-macro-information"><p class="title">Why the S in SJMS</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><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/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)"></p></div></div><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="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-sjms</artifactId>
@@ -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&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/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> </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 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"> </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: </span><code>default</code><span style="color: rgb(0,0,0);"> and </span><code>passthrough</code><span style="color: rgb(0,0,0);">. The </span><code>default</code><span style="color: rgb(0,0,0);"> strategy will safely marshal dots and hyphens (</span><code>.</code><span style="color: rgb(0,0,0);"> and </span><code>-</code><span style="color:
rgb(0,0,0);">). The </span><code>passthrough</code><span style="color: rgb(0,0,0);"> 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);"> and refer to it using the </span><code>#</code><span style="color: rgb(0,0,0);"> 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> </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><tr><td colspan="1" rowspan="1" class="confluenceTd"><code>DestinationCreationStrategy</code></td><td colspan="1" rowspan="1" class="confluenceTd"> </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"> </td><td colspan="1" rowspan="1" class="confluenceTd"> </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"> </td><td colspan="1" rowspan="1" class="confluenceTd"> </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"> </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>
+</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/5997/6f42626d00e36f53fe51440403446ca61552e2a2.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 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"> </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: </span><code>default</code><span style="color: rgb(0,0,0);"> and </span><code>passthrough</code><span style="color: rgb(0,0,0);">. The </span><code>default</code><span style="color: rgb(0,0,0);"> strategy will safely marshal dots and hyphens (</span><code>.</code><span style="color: rgb(0,0,0);"> and </span><code>-</code><span style="color:
rgb(0,0,0);">). The </span><code>passthrough</code><span style="color: rgb(0,0,0);"> 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);"> and refer to it using the </span><code>#</code><span style="color: rgb(0,0,0);"> 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> </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><tr><td colspan="1" rowspan="1" class="confluenceTd"><code>DestinationCreationStrategy</code></td><td colspan="1" rowspan="1" class="confluenceTd"> </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"> </td><td colspan="1" rowspan="1" class="confluenceTd"> </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"> </td><td colspan="1" rowspan="1" class="confluenceTd"> </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"> </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 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">
Modified: websites/production/camel/content/spark-rest.html
==============================================================================
--- websites/production/camel/content/spark-rest.html (original)
+++ websites/production/camel/content/spark-rest.html Thu Jun 15 16:25:44 2017
@@ -117,8 +117,9 @@
}
};]]></script>
</div></div>
-</div>
-<div class="tabs-pane" id="RestDslTabsXml" data-pane-title="XML">
+
+
+</div><div class="tabs-pane" id="RestDslTabsXml" data-pane-title="XML">
<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[ <camelContext xmlns="http://camel.apache.org/schema/spring">
<rest uri="/hello/{me}">
@@ -132,10 +133,11 @@
</rest>
</camelContext>]]></script>
</div></div>
+
+
</div>
</div>
-<div style="clear:both"><p> </p></div>
-<p><span style="line-height: 1.4285715;">See more details at the </span><a shape="rect" href="rest-dsl.html">Rest DSL</a><span style="line-height: 1.4285715;">.</span></p><h3 id="Spark-rest-Moreexamples"><span style="font-size: 16.0px;line-height: 1.5625;">More examples</span></h3><p>There is a <strong>camel-example-spark-rest-tomcat</strong> example in the Apache Camel distribution, that demonstrates how to use camel-spark-rest in a web application that can be deployed on Apache Tomcat, or similar web containers.</p><p></p><h3 id="Spark-rest-SeeAlso">See Also</h3>
+<div style="clear:both"><p> </p></div><p><span style="line-height: 1.4285715;">See more details at the </span><a shape="rect" href="rest-dsl.html">Rest DSL</a><span style="line-height: 1.4285715;">.</span></p><h3 id="Spark-rest-Moreexamples"><span style="font-size: 16.0px;line-height: 1.5625;">More examples</span></h3><p>There is a <strong>camel-example-spark-rest-tomcat</strong> example in the Apache Camel distribution, that demonstrates how to use camel-spark-rest in a web application that can be deployed on Apache Tomcat, or similar web containers.</p><p></p><h3 id="Spark-rest-SeeAlso">See Also</h3>
<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul><ul style="list-style-type: square;"><li><a shape="rect" href="rest.html">Rest</a></li></ul></div>
</td>
<td valign="top">
Modified: websites/production/camel/content/support.html
==============================================================================
--- websites/production/camel/content/support.html (original)
+++ websites/production/camel/content/support.html Thu Jun 15 16:25:44 2017
@@ -75,7 +75,7 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2 id="Support-GettingHelp">Getting Help</h2><p>If you are experiencing problems using Camel then please report your problem to our <a shape="rect" href="discussion-forums.html">Discussion Forums</a>. This allows the entire community to help with your problem. If indeed a bug has been identified in the Camel software, then document the problem in our <a shape="rect" class="external-link" href="http://issues.apache.org/jira/browse/CAMEL">Issue Tracker</a>. Please refrain from immediately opening a ticket in the issue tracker unless you are certain it's a problem in the Camel software. If you are in doubt, we appreciate asking the <a shape="rect" href="discussion-forums.html">Discussion Forums</a> first.</p><div class="confluence-information-macro confluence-information-macro-tip"><span class="aui-icon aui-icon-small aui-iconfont-approve confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>Please read the se
ction below (<em>How to get help</em>), and follow the bullets advised there first.</p></div></div><div class="confluence-information-macro confluence-information-macro-information"><p class="title">Reporting bugs - Please read this first</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>We prefer people to get in touch first using the mailing list or forums. Or take time to read FAQs, or search in the mailing list archives to find answers.<br clear="none"> Unfortunately some people create a JIRA ticket as first thing. Please don't do that! Only if you are sure it really is a bug etc. JIRA tickets create noise<br clear="none"> for the Camel team to react on issues that are not bugs. But already covered in FAQs, in the mailing lists/forums etc. Or in the existing documentation.<br clear="none"> Also on the mailing lists / forums, there is more people active to help you better.</p></div
></div><ul><li><a shape="rect" class="external-link" href="http://issues.apache.org/jira/browse/CAMEL">Issue Tracker</a></li><li><a shape="rect" class="external-link" href="http://camel.apache.org/discussion-forums.html">Discussion Forums</a></li><li><a shape="rect" href="faq.html">FAQ</a></li></ul><h3 id="Support-Alternativediscussionforums">Alternative discussion forums</h3><p>There's a number of sites outside Apache that offer discussion forums on Camel. For example, <a shape="rect" class="external-link" href="http://stackoverflow.com/" rel="nofollow">Stack Overflow</a> is a popular Q & A site with a <a shape="rect" class="external-link" href="http://stackoverflow.com/questions/tagged/apache-camel" rel="nofollow">dedicated Apache Camel forum</a>. You are also likely to find helpful discussions on technical blogs, on <a shape="rect" class="external-link" href="https://www.google.com/search?q=apache+camel" rel="nofollow">Google</a>, or even on <a shape="rect" class="e
xternal-link" href="https://twitter.com/#!/search/apache%20camel" rel="nofollow">Twitter</a>.</p><h3 id="Support-Usingdeprecatedcomponents">Using deprecated components</h3><p>Deprecated components are <strong>not</strong> supported and issues such as bugs may not be fixed. We encourage users to migrate away from using any deprecated component. A list of deprecated components is listed on the github page at: <a shape="rect" class="external-link" href="https://github.com/apache/camel/tree/master/components#components" rel="nofollow">https://github.com/apache/camel/tree/master/components#components</a></p><h3 id="Support-Howtogethelp">How to get help</h3><p>Before you report a problem, you may wish to read the <a shape="rect" href="faq.html">FAQ</a>. <br clear="none"> When you report an issue, please be sure to include as much information as possible. The more we know, the easier it is to reach an effective solution quickly.</p><div class="confluence-information-macro conflue
nce-information-macro-note"><p class="title">What version do you use</p><span class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>What version of Camel do you use! Remember to include this information.</p></div></div><ul><li><strong>what are the version numbers of involved software components?</strong> (this is very important to detail)</li><li>what platform and JDK?</li><li>any particular container being used? and if so, what version?</li><li>stack traces generally really help! (<strong>Remember to post which version of Camel you use, this is important to know when posting stacktraces</strong>) If in doubt, include the whole thing; often exceptions get wrapped in other exceptions and the exception right near the bottom explains the actual error, not the first few lines at the top. It's very easy for us to skim-read past unnecessary parts of a stack trace.</li><li>log output can be useful too
; sometimes <a shape="rect" href="how-do-i-change-the-logging.html">enabling DEBUG logging</a> can help</li><li>your code & configuration files are often useful</li><li>did it work before? what have you changed to break it?</li><li>try upgrading to the latest release and see if it's fixed there</li><li>try the latest SNAPSHOT to see if it's fixed in the pre-release</li><li>search the user forum to see if has been discussed before</li><li>see the "known issues" section in the release notes</li><li>and check the <a shape="rect" class="external-link" href="http://issues.apache.org/jira/browse/CAMEL">issue tracker</a> to see if the issue has already been reported</li><li>do <strong>not</strong> send private emails to Camel <a shape="rect" href="team.html">Team</a> members to ask them to help you faster, or in the private only. Help on Apache Camel is volunteer based and <strong>must</strong> happen in the <strong>open</strong> on the public <a shape="rect" href="mailing-lists.html">
Mailing Lists</a> or <a shape="rect" href="discussion-forums.html">Discussion Forums</a>. If you want to get help faster or in private, then see further below.</li></ul><h3 id="Support-Howtogethelpfaster">How to get help faster</h3><p>We can help you much quicker if you try the following</p><ul><li>provide us with a JUnit test case that demonstrates your issue. e.g. if you think you've found a bug, can you create a test case to demonstrate the bug?</li><li><a shape="rect" class="external-link" href="http://camel.apache.org/contributing.html">submit a patch</a> fixing the bug! (We also buy you beer when we meet you if you submit bug fixes <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)"> )</li><li>for memory leak or performance related issues, if you can run a profiler on your test case and attach the output as a file (or zi
pped file if it's huge) to the JIRA we can normally fix things much faster. e.g. you could run <a shape="rect" class="external-link" href="http://java.sun.com/j2se/1.5.0/docs/tooldocs/share/jmap.html" rel="nofollow">jmap</a>/<a shape="rect" class="external-link" href="http://java.sun.com/javase/6/docs/technotes/tools/share/jhat.html" rel="nofollow">jhat</a>, JProfiler or YourKit on your code and send us the output. To find memory leaks it's quicker to resolve if you can tell us what classes are taking up all of the RAM; we can normally figure out what's wrong from that.</li></ul><h2 id="Support-CommercialSupport">Commercial Support</h2><p>This is an open source project, so the amount of time we have available to help resolve your issue is often limited as all help is provided on a volunteer basis. If you want to get priority help, need to get up to speed quickly, require some training or mentoring, or need full 24 x 7 production support you could contact one of the following compani
es with <a shape="rect" href="commercial-camel-offerings.html">Commercial Camel Offerings</a>.</p></div>
+<div class="wiki-content maincontent"><h2 id="Support-GettingHelp">Getting Help</h2><p>If you are experiencing problems using Camel then please report your problem to our <a shape="rect" href="discussion-forums.html">Discussion Forums</a>. This allows the entire community to help with your problem. If indeed a bug has been identified in the Camel software, then document the problem in our <a shape="rect" class="external-link" href="http://issues.apache.org/jira/browse/CAMEL">Issue Tracker</a>. Please refrain from immediately opening a ticket in the issue tracker unless you are certain it's a problem in the Camel software. If you are in doubt, we appreciate asking the <a shape="rect" href="discussion-forums.html">Discussion Forums</a> first.</p><div class="confluence-information-macro confluence-information-macro-tip"><span class="aui-icon aui-icon-small aui-iconfont-approve confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>Please read the se
ction below (<em>How to get help</em>), and follow the bullets advised there first.</p></div></div><div class="confluence-information-macro confluence-information-macro-information"><p class="title">Reporting bugs - Please read this first</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>We prefer people to get in touch first using the mailing list or forums. Or take time to read FAQs, or search in the mailing list archives to find answers.<br clear="none"> Unfortunately some people create a JIRA ticket as first thing. Please don't do that! Only if you are sure it really is a bug etc. JIRA tickets create noise<br clear="none"> for the Camel team to react on issues that are not bugs. But already covered in FAQs, in the mailing lists/forums etc. Or in the existing documentation.<br clear="none"> Also on the mailing lists / forums, there is more people active to help you better.</p></div
></div><ul><li><a shape="rect" class="external-link" href="http://issues.apache.org/jira/browse/CAMEL">Issue Tracker</a></li><li><a shape="rect" class="external-link" href="http://camel.apache.org/discussion-forums.html">Discussion Forums</a></li><li><a shape="rect" href="faq.html">FAQ</a></li></ul><h3 id="Support-Alternativediscussionforums">Alternative discussion forums</h3><p>There's a number of sites outside Apache that offer discussion forums on Camel. For example, <a shape="rect" class="external-link" href="http://stackoverflow.com/" rel="nofollow">Stack Overflow</a> is a popular Q & A site with a <a shape="rect" class="external-link" href="http://stackoverflow.com/questions/tagged/apache-camel" rel="nofollow">dedicated Apache Camel forum</a>. You are also likely to find helpful discussions on technical blogs, on <a shape="rect" class="external-link" href="https://www.google.com/search?q=apache+camel" rel="nofollow">Google</a>, or even on <a shape="rect" class="e
xternal-link" href="https://twitter.com/#!/search/apache%20camel" rel="nofollow">Twitter</a>.</p><h3 id="Support-Usingdeprecatedcomponents">Using deprecated components</h3><p>Deprecated components are <strong>not</strong> supported and issues such as bugs may not be fixed. We encourage users to migrate away from using any deprecated component. A list of deprecated components is listed on the github page at: <a shape="rect" class="external-link" href="https://github.com/apache/camel/tree/master/components#components" rel="nofollow">https://github.com/apache/camel/tree/master/components#components</a></p><h3 id="Support-Howtogethelp">How to get help</h3><p>Before you report a problem, you may wish to read the <a shape="rect" href="faq.html">FAQ</a>. <br clear="none"> When you report an issue, please be sure to include as much information as possible. The more we know, the easier it is to reach an effective solution quickly.</p><div class="confluence-information-macro conflue
nce-information-macro-note"><p class="title">What version do you use</p><span class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>What version of Camel do you use! Remember to include this information.</p></div></div><ul><li><strong>what are the version numbers of involved software components?</strong> (this is very important to detail)</li><li>what platform and JDK?</li><li>any particular container being used? and if so, what version?</li><li>stack traces generally really help! (<strong>Remember to post which version of Camel you use, this is important to know when posting stacktraces</strong>) If in doubt, include the whole thing; often exceptions get wrapped in other exceptions and the exception right near the bottom explains the actual error, not the first few lines at the top. It's very easy for us to skim-read past unnecessary parts of a stack trace.</li><li>log output can be useful too
; sometimes <a shape="rect" href="how-do-i-change-the-logging.html">enabling DEBUG logging</a> can help</li><li>your code & configuration files are often useful</li><li>did it work before? what have you changed to break it?</li><li>try upgrading to the latest release and see if it's fixed there</li><li>try the latest SNAPSHOT to see if it's fixed in the pre-release</li><li>search the user forum to see if has been discussed before</li><li>see the "known issues" section in the release notes</li><li>and check the <a shape="rect" class="external-link" href="http://issues.apache.org/jira/browse/CAMEL">issue tracker</a> to see if the issue has already been reported</li><li>do <strong>not</strong> send private emails to Camel <a shape="rect" href="team.html">Team</a> members to ask them to help you faster, or in the private only. Help on Apache Camel is volunteer based and <strong>must</strong> happen in the <strong>open</strong> on the public <a shape="rect" href="mailing-lists.html">
Mailing Lists</a> or <a shape="rect" href="discussion-forums.html">Discussion Forums</a>. If you want to get help faster or in private, then see further below.</li></ul><h3 id="Support-Howtogethelpfaster">How to get help faster</h3><p>We can help you much quicker if you try the following</p><ul><li>provide us with a JUnit test case that demonstrates your issue. e.g. if you think you've found a bug, can you create a test case to demonstrate the bug?</li><li><a shape="rect" class="external-link" href="http://camel.apache.org/contributing.html">submit a patch</a> fixing the bug! (We also buy you beer when we meet you if you submit bug fixes <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)"> )</li><li>for memory leak or performance related issues, if you can run a profiler on your test case and attach the output as a file (or zi
pped file if it's huge) to the JIRA we can normally fix things much faster. e.g. you could run <a shape="rect" class="external-link" href="http://java.sun.com/j2se/1.5.0/docs/tooldocs/share/jmap.html" rel="nofollow">jmap</a>/<a shape="rect" class="external-link" href="http://java.sun.com/javase/6/docs/technotes/tools/share/jhat.html" rel="nofollow">jhat</a>, JProfiler or YourKit on your code and send us the output. To find memory leaks it's quicker to resolve if you can tell us what classes are taking up all of the RAM; we can normally figure out what's wrong from that.</li></ul><h2 id="Support-CommercialSupport">Commercial Support</h2><p>This is an open source project, so the amount of time we have available to help resolve your issue is often limited as all help is provided on a volunteer basis. If you want to get priority help, need to get up to speed quickly, require some training or mentoring, or need full 24 x 7 production support you could contact one of the following compani
es with <a shape="rect" href="commercial-camel-offerings.html">Commercial Camel Offerings</a>.</p></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/camel/content/tar-dataformat.html
==============================================================================
--- websites/production/camel/content/tar-dataformat.html (original)
+++ websites/production/camel/content/tar-dataformat.html Thu Jun 15 16:25:44 2017
@@ -91,7 +91,7 @@
<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[from("file:input/directory?antInclude=*/.txt").marshal().tarFile().to("file:output/directory");]]></script>
</div></div><div><span>If there is no incoming </span><code>CamelFileName</code><span> message header (for example, if the </span><a shape="rect" class="external-link" href="https://github.com/apache/camel/blob/master/components/camel-tarfile/src/main/docs/file2.html" rel="nofollow">file component</a><span> is not the consumer), then the message ID is used by default, and since the message ID is normally a unique generated ID, you will end up with filenames like </span><code>ID-MACHINENAME-2443-1211718892437-1-0.tar</code><span>. If you want to override this behavior, then you can set the value of the </span><code>CamelFileName</code><span> header explicitly in your route:</span></div><div><p> </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[from("direct:start").setHeader(Exchange.FILE_NAME, constant("report.txt")).marshal().tarFile().to("file:output/directory");]]></script>
-</div></div><div><div><p>This route would result in a Tar File named "report.txt.tar" in the output directory, containing a single Tar entry named "report.txt".</p><p> </p></div></div><div><h4 id="TarDataFormat-UUnmarshal"><a shape="rect" class="external-link" href="https://github.com/apache/camel/blob/master/components/camel-tarfile/src/main/docs/tarfile-dataformat.adoc#unmarshal" style="" rel="nofollow"></a>UUnmarshal</h4><div><p>In this example we unmarshal a Tar File payload from an ActiveMQ queue called MY_QUEUE to its original format, and forward it for processing to the <code>UnTarpedMessageProcessor</code>.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><div><div><p>This route would result in a Tar File named "report.txt.tar" in the output directory, containing a single Tar entry named "report.txt".</p><p> </p></div></div><div><h4 id="TarDataFormat-UUnmarshal"><a shape="rect" class="external-link" href="https://github.com/apache/camel/blob/master/components/camel-tarfile/src/main/docs/tarfile-dataformat.adoc#unmarshal" rel="nofollow" style=""></a>UUnmarshal</h4><div><p>In this example we unmarshal a Tar File payload from an ActiveMQ queue called MY_QUEUE to its original format, and forward it for processing to the <code>UnTarpedMessageProcessor</code>.</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[from("activemq:queue:MY_QUEUE").unmarshal().tarFile().process(new UnTarpedMessageProcessor()); ]]></script>
</div></div><div><span>If the Tar File has more then one entry, the usingIterator option of TarFileDataFormat to be true, and you can use splitter to do the further work.</span></div><div><p> </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[TarFileDataFormat tarFile = new TarFileDataFormat();