Author: buildbot
Date: Sat May 26 19:20:21 2012
New Revision: 819204
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/book-component-appendix.html
websites/production/camel/content/book-in-one-page.html
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/jms.html
Modified: websites/production/camel/content/book-component-appendix.html
==============================================================================
--- websites/production/camel/content/book-component-appendix.html (original)
+++ websites/production/camel/content/book-component-appendix.html Sat May 26
19:20:21 2012
@@ -9282,13 +9282,6 @@ from(aaa)
<ul><li><tt>transacted</tt> = true</li><li><tt>transactionManager</tt> = a
<em>Transsaction Manager</em> - typically the
<tt>JmsTransactionManager</tt></li></ul>
-<p>From Camel 2.10 onwards you can leverage the <a shape="rect"
class="external-link"
href="http://static.springsource.org/spring/docs/3.0.x/javadoc-api/org/springframework/jms/listener/AbstractPollingMessageListenerContainer.html#setSessionTransacted(boolean)"
rel="nofollow">DMLC transacted session API</a> using the following properties
on component/endpoint:</p>
-
-<ul><li><tt>transacted</tt> =
true</li><li><tt>lazyCreateTransactionManager</tt> = false</li></ul>
-
-
-<p>The benefit of doing so is that the cacheLevel setting will be honored when
using local transactions without a configured TransactionManager. When a
TransactionManager is configured, no caching happens at DMLC level and its
necessary to rely on a pooled connection factory. This was discussed <a
shape="rect" class="external-link"
href="http://tmielke.blogspot.com/2012/03/camel-jms-with-transactions-lessons.html";
rel="nofollow">here</a> and <a shape="rect" class="external-link"
href="http://forum.springsource.org/showthread.php?123631-JMS-DMLC-not-caching
connection-when-using-TX-despite-cacheLevel-CACHE_CONSUMER&p=403530&posted=1#post403530"
rel="nofollow">here</a> before this was provided by Camel.</p>
-
<p>See the <a shape="rect" href="transactional-client.html"
title="Transactional Client">Transactional Client</a> EIP pattern for further
details.</p>
<div class="panelMacro"><table class="infoMacro"><colgroup span="1"><col
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1"
valign="top"><img align="middle"
src="https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif";
width="16" height="16" alt="" border="0"></td><td colspan="1"
rowspan="1"><b>Transactions and <a shape="rect" href="request-reply.html"
title="Request Reply">Request Reply</a> over JMS</b><br clear="none">When using
<a shape="rect" href="request-reply.html" title="Request Reply">Request
Reply</a> over JMS you cannot use a single transaction; JMS will not send any
messages until a commit is performed, so the server side won't receive anything
at all until the transaction commits. Therefore to use <a shape="rect"
href="request-reply.html" title="Request Reply">Request Reply</a> you must
commit a transaction after sending the request and then use a separate
transaction for receiving the response.
@@ -9301,6 +9294,15 @@ from(aaa)
<p>If you want to use transactions for <a shape="rect"
href="request-reply.html" title="Request Reply">Request Reply</a>(InOut MEP),
you <b>must</b> set <tt>transactedInOut=true</tt>.</p></td></tr></table></div>
+<p><b>Available as of Camel 2.10</b></p>
+
+<p>You can leverage the <a shape="rect" class="external-link"
href="http://static.springsource.org/spring/docs/3.0.x/javadoc-api/org/springframework/jms/listener/AbstractPollingMessageListenerContainer.html#setSessionTransacted(boolean)"
rel="nofollow">DMLC transacted session API</a> using the following properties
on component/endpoint:</p>
+
+<ul><li><tt>transacted</tt> =
true</li><li><tt>lazyCreateTransactionManager</tt> = false</li></ul>
+
+
+<p>The benefit of doing so is that the cacheLevel setting will be honored when
using local transactions without a configured TransactionManager. When a
TransactionManager is configured, no caching happens at DMLC level and its
necessary to rely on a pooled connection factory. For more details about this
kind of setup see <a shape="rect" class="external-link"
href="http://tmielke.blogspot.com/2012/03/camel-jms-with-transactions-lessons.html";
rel="nofollow">here</a> and <a shape="rect" class="external-link"
href="http://forum.springsource.org/showthread.php?123631-JMS-DMLC-not-caching
connection-when-using-TX-despite-cacheLevel-CACHE_CONSUMER&p=403530&posted=1#post403530"
rel="nofollow">here</a>.</p>
+
<h3><a shape="rect"
name="BookComponentAppendix-UsingJMSReplyToforlatereplies"></a>Using JMSReplyTo
for late replies</h3>
Modified: websites/production/camel/content/book-in-one-page.html
==============================================================================
--- websites/production/camel/content/book-in-one-page.html (original)
+++ websites/production/camel/content/book-in-one-page.html Sat May 26 19:20:21
2012
@@ -29691,13 +29691,6 @@ from(aaa)
<ul><li><tt>transacted</tt> = true</li><li><tt>transactionManager</tt> = a
<em>Transsaction Manager</em> - typically the
<tt>JmsTransactionManager</tt></li></ul>
-<p>From Camel 2.10 onwards you can leverage the <a shape="rect"
class="external-link"
href="http://static.springsource.org/spring/docs/3.0.x/javadoc-api/org/springframework/jms/listener/AbstractPollingMessageListenerContainer.html#setSessionTransacted(boolean)"
rel="nofollow">DMLC transacted session API</a> using the following properties
on component/endpoint:</p>
-
-<ul><li><tt>transacted</tt> =
true</li><li><tt>lazyCreateTransactionManager</tt> = false</li></ul>
-
-
-<p>The benefit of doing so is that the cacheLevel setting will be honored when
using local transactions without a configured TransactionManager. When a
TransactionManager is configured, no caching happens at DMLC level and its
necessary to rely on a pooled connection factory. This was discussed <a
shape="rect" class="external-link"
href="http://tmielke.blogspot.com/2012/03/camel-jms-with-transactions-lessons.html";
rel="nofollow">here</a> and <a shape="rect" class="external-link"
href="http://forum.springsource.org/showthread.php?123631-JMS-DMLC-not-caching
connection-when-using-TX-despite-cacheLevel-CACHE_CONSUMER&p=403530&posted=1#post403530"
rel="nofollow">here</a> before this was provided by Camel.</p>
-
<p>See the <a shape="rect" href="transactional-client.html"
title="Transactional Client">Transactional Client</a> EIP pattern for further
details.</p>
<div class="panelMacro"><table class="infoMacro"><colgroup span="1"><col
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1"
valign="top"><img align="middle"
src="https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif";
width="16" height="16" alt="" border="0"></td><td colspan="1"
rowspan="1"><b>Transactions and <a shape="rect" href="request-reply.html"
title="Request Reply">Request Reply</a> over JMS</b><br clear="none">When using
<a shape="rect" href="request-reply.html" title="Request Reply">Request
Reply</a> over JMS you cannot use a single transaction; JMS will not send any
messages until a commit is performed, so the server side won't receive anything
at all until the transaction commits. Therefore to use <a shape="rect"
href="request-reply.html" title="Request Reply">Request Reply</a> you must
commit a transaction after sending the request and then use a separate
transaction for receiving the response.
@@ -29710,6 +29703,15 @@ from(aaa)
<p>If you want to use transactions for <a shape="rect"
href="request-reply.html" title="Request Reply">Request Reply</a>(InOut MEP),
you <b>must</b> set <tt>transactedInOut=true</tt>.</p></td></tr></table></div>
+<p><b>Available as of Camel 2.10</b></p>
+
+<p>You can leverage the <a shape="rect" class="external-link"
href="http://static.springsource.org/spring/docs/3.0.x/javadoc-api/org/springframework/jms/listener/AbstractPollingMessageListenerContainer.html#setSessionTransacted(boolean)"
rel="nofollow">DMLC transacted session API</a> using the following properties
on component/endpoint:</p>
+
+<ul><li><tt>transacted</tt> =
true</li><li><tt>lazyCreateTransactionManager</tt> = false</li></ul>
+
+
+<p>The benefit of doing so is that the cacheLevel setting will be honored when
using local transactions without a configured TransactionManager. When a
TransactionManager is configured, no caching happens at DMLC level and its
necessary to rely on a pooled connection factory. For more details about this
kind of setup see <a shape="rect" class="external-link"
href="http://tmielke.blogspot.com/2012/03/camel-jms-with-transactions-lessons.html";
rel="nofollow">here</a> and <a shape="rect" class="external-link"
href="http://forum.springsource.org/showthread.php?123631-JMS-DMLC-not-caching
connection-when-using-TX-despite-cacheLevel-CACHE_CONSUMER&p=403530&posted=1#post403530"
rel="nofollow">here</a>.</p>
+
<h3><a shape="rect"
name="BookInOnePage-UsingJMSReplyToforlatereplies"></a>Using JMSReplyTo for
late replies</h3>
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/jms.html
==============================================================================
--- websites/production/camel/content/jms.html (original)
+++ websites/production/camel/content/jms.html Sat May 26 19:20:21 2012
@@ -510,13 +510,6 @@ from(aaa)
<ul><li><tt>transacted</tt> = true</li><li><tt>transactionManager</tt> = a
<em>Transsaction Manager</em> - typically the
<tt>JmsTransactionManager</tt></li></ul>
-<p>From Camel 2.10 onwards you can leverage the <a shape="rect"
class="external-link"
href="http://static.springsource.org/spring/docs/3.0.x/javadoc-api/org/springframework/jms/listener/AbstractPollingMessageListenerContainer.html#setSessionTransacted(boolean)"
rel="nofollow">DMLC transacted session API</a> using the following properties
on component/endpoint:</p>
-
-<ul><li><tt>transacted</tt> =
true</li><li><tt>lazyCreateTransactionManager</tt> = false</li></ul>
-
-
-<p>The benefit of doing so is that the cacheLevel setting will be honored when
using local transactions without a configured TransactionManager. When a
TransactionManager is configured, no caching happens at DMLC level and its
necessary to rely on a pooled connection factory. This was discussed <a
shape="rect" class="external-link"
href="http://tmielke.blogspot.com/2012/03/camel-jms-with-transactions-lessons.html";
rel="nofollow">here</a> and <a shape="rect" class="external-link"
href="http://forum.springsource.org/showthread.php?123631-JMS-DMLC-not-caching
connection-when-using-TX-despite-cacheLevel-CACHE_CONSUMER&p=403530&posted=1#post403530"
rel="nofollow">here</a> before this was provided by Camel.</p>
-
<p>See the <a shape="rect" href="transactional-client.html"
title="Transactional Client">Transactional Client</a> EIP pattern for further
details.</p>
<div class="panelMacro"><table class="infoMacro"><colgroup span="1"><col
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1"
valign="top"><img align="middle"
src="https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif";
width="16" height="16" alt="" border="0"></td><td colspan="1"
rowspan="1"><b>Transactions and <a shape="rect" href="request-reply.html"
title="Request Reply">Request Reply</a> over JMS</b><br clear="none">When using
<a shape="rect" href="request-reply.html" title="Request Reply">Request
Reply</a> over JMS you cannot use a single transaction; JMS will not send any
messages until a commit is performed, so the server side won't receive anything
at all until the transaction commits. Therefore to use <a shape="rect"
href="request-reply.html" title="Request Reply">Request Reply</a> you must
commit a transaction after sending the request and then use a separate
transaction for receiving the response.
@@ -529,6 +522,15 @@ from(aaa)
<p>If you want to use transactions for <a shape="rect"
href="request-reply.html" title="Request Reply">Request Reply</a>(InOut MEP),
you <b>must</b> set <tt>transactedInOut=true</tt>.</p></td></tr></table></div>
+<p><b>Available as of Camel 2.10</b></p>
+
+<p>You can leverage the <a shape="rect" class="external-link"
href="http://static.springsource.org/spring/docs/3.0.x/javadoc-api/org/springframework/jms/listener/AbstractPollingMessageListenerContainer.html#setSessionTransacted(boolean)"
rel="nofollow">DMLC transacted session API</a> using the following properties
on component/endpoint:</p>
+
+<ul><li><tt>transacted</tt> =
true</li><li><tt>lazyCreateTransactionManager</tt> = false</li></ul>
+
+
+<p>The benefit of doing so is that the cacheLevel setting will be honored when
using local transactions without a configured TransactionManager. When a
TransactionManager is configured, no caching happens at DMLC level and its
necessary to rely on a pooled connection factory. For more details about this
kind of setup see <a shape="rect" class="external-link"
href="http://tmielke.blogspot.com/2012/03/camel-jms-with-transactions-lessons.html";
rel="nofollow">here</a> and <a shape="rect" class="external-link"
href="http://forum.springsource.org/showthread.php?123631-JMS-DMLC-not-caching
connection-when-using-TX-despite-cacheLevel-CACHE_CONSUMER&p=403530&posted=1#post403530"
rel="nofollow">here</a>.</p>
+
<h3><a shape="rect" name="JMS-UsingJMSReplyToforlatereplies"></a>Using
JMSReplyTo for late replies</h3>
![https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif"](https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif"){kind=link}