[jboss-cvs] JBossAS SVN: r95663 - projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed Oct 28 03:17:16 EDT 2009
Author: laubai
Date: 2009-10-28 03:17:16 -0400 (Wed, 28 Oct 2009)
New Revision: 95663
Modified:
projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Transactions.xml
Log:
Added changes for JBPAPP-2622.
Modified: projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Transactions.xml
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Transactions.xml 2009-10-28 07:00:23 UTC (rev 95662)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Transactions.xml 2009-10-28 07:17:16 UTC (rev 95663)
@@ -212,7 +212,7 @@
</section>
<section>
<title>Transactional Resources</title>
- <para>The transaction manger coordinates the update of state via XAResource
+ <para>The transaction manager coordinates the update of state via XAResource
implementations, which are provided by the various resource managers. In
most instances, resource managers will be databases, message queues or 3rd
party JCA resource adapters. The list of JDBC database drivers and servers
@@ -229,7 +229,7 @@
participate correctly in an ongoing transaction. This is the dominant use
case and should be preferred where transactional guarantees for data access
are required. For cases where the database cannot support XA transactions,
- it it also feasible to deploy a connection pool using
+ it is also feasible to deploy a connection pool using
<![CDATA[<local-xa-datasource>]]> Such datasources participate in the
managed transaction using the last resource commit optimization (see below)
and as such provide more limited transactional guarantees. Applications
More information about the jboss-cvs-commits
mailing list