[jboss-cvs] JBoss Messaging SVN: r8064 - branches/Branch_1_4/docs/userguide/en/modules.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Jul 1 05:02:41 EDT 2010
Author: gaohoward
Date: 2010-07-01 05:02:41 -0400 (Thu, 01 Jul 2010)
New Revision: 8064
Modified:
branches/Branch_1_4/docs/userguide/en/modules/configuration.xml
Log:
JBMESSAGING-1788
Modified: branches/Branch_1_4/docs/userguide/en/modules/configuration.xml
===================================================================
--- branches/Branch_1_4/docs/userguide/en/modules/configuration.xml 2010-06-25 15:39:54 UTC (rev 8063)
+++ branches/Branch_1_4/docs/userguide/en/modules/configuration.xml 2010-07-01 09:02:41 UTC (rev 8064)
@@ -625,6 +625,29 @@
you need to update all the <literal>DataSource</literal> attribute in the
persistence configuration file. Example data source configurations for
each of the popular databases are available in the distribution.</para>
+
+ <warning>
+ <para>JBoss Messaging fully supports XA transactional resource interface. This
+ enables JBoss Messaging to be enlisted in a global transaction. However, this functionality
+ has nothing to do with the datasources it uses for persistence. In other words, JBoss
+ Messaging does not use, and should not use, an XA database datasource for its persistence.
+ That means the configuration of the datasource to which JBoss Messaging references in its
+ persistence configuration file must be one defined in <local-tx-datasource> entry in the datasource
+ configuration file. For example </para>
+<programlisting>
+<datasources>
+ <local-tx-datasource>
+ <jndi-name>DefaultDS</jndi-name>
+ <connection-url>jdbc:mysql://localhost:3306/messaging</connection-url>
+ <driver-class>com.mysql.jdbc.Driver</driver-class>
+ <user-name>sa</user-name>
+ <password></password>
+ ... ...
+ </local-tx-datasource>
+</datasources>
+</programlisting>
+ </warning>
+
</section>
<section id="conf.postoffice">
More information about the jboss-cvs-commits
mailing list