From 09cd014b7bd39b6cc56df3b80078f8316ba09709 Mon Sep 17 00:00:00 2001 From: Mattias Arthursson Date: Wed, 18 Jun 2008 12:40:12 +0000 Subject: [PATCH] Fixed inconsistent entry in reference documentation. --- mvn-build/core/docs/reference/src/transactions.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/mvn-build/core/docs/reference/src/transactions.xml b/mvn-build/core/docs/reference/src/transactions.xml index b456e277..39786fed 100644 --- a/mvn-build/core/docs/reference/src/transactions.xml +++ b/mvn-build/core/docs/reference/src/transactions.xml @@ -100,8 +100,8 @@ access within the same transaction using the ContextSourceAndDataSourceTransactionManager. A DataSource and a ContextSource is supplied to the ContextSourceAndDataSourceTransactionManager, which will then manage the two transactions, - virtually as if they were one. When performing a commit, the LDAP part of the operation will always - be performed first, allowing both transactions to be rolled back should the LDAP commit fail. The JDBC + virtually as if they were one. When performing a commit, the JDBC part of the operation will always + be performed first, allowing both transactions to be rolled back should the JDBC commit fail. The JDBC part of the transaction is managed exactly as in DataSourceTransactionManager, except that nested transactions is not supported. Once again it should be noted that the provided support is all client side. The wrapped transaction is not