[jboss-cvs] JBossAS SVN: r105406 - in projects/docs/enterprise/EAP/trunk/5.x: Hibernate_Core_Reference_Guide/en-US and 1 other directory.

[jboss-cvs-commits at lists.jboss.org]

Author: rebecca_newton
Date: 2010-05-31 03:21:52 -0400 (Mon, 31 May 2010)
New Revision: 105406

Modified:
   projects/docs/enterprise/EAP/trunk/5.x/Administration_And_Configuration_Guide/en-US/Clustering_Guide_JBoss_Cache.xml
   projects/docs/enterprise/EAP/trunk/5.x/Administration_And_Configuration_Guide/en-US/Transactions.xml
   projects/docs/enterprise/EAP/trunk/5.x/Hibernate_Core_Reference_Guide/en-US/transactions.xml
Log:
JIRA fixes

Modified: projects/docs/enterprise/EAP/trunk/5.x/Administration_And_Configuration_Guide/en-US/Clustering_Guide_JBoss_Cache.xml
===================================================================
--- projects/docs/enterprise/EAP/trunk/5.x/Administration_And_Configuration_Guide/en-US/Clustering_Guide_JBoss_Cache.xml	2010-05-31 06:20:47 UTC (rev 105405)
+++ projects/docs/enterprise/EAP/trunk/5.x/Administration_And_Configuration_Guide/en-US/Clustering_Guide_JBoss_Cache.xml	2010-05-31 07:21:52 UTC (rev 105406)
@@ -410,13 +410,6 @@
              </para>
            </listitem>
          </itemizedlist>
-         
-         <note>
-           <para>For caches used for JPA/Hibernate caching, the 
-           <literal>transactionManagerLookupClass</literal> should not be
-           configured.  Hibernate internally configures the cache to use
-           the same transaction manager it is using for database access.</para>
-         </note>
       </section>
       
       <section id="jbosscache-configuration-concurrency">

Modified: projects/docs/enterprise/EAP/trunk/5.x/Administration_And_Configuration_Guide/en-US/Transactions.xml
===================================================================
--- projects/docs/enterprise/EAP/trunk/5.x/Administration_And_Configuration_Guide/en-US/Transactions.xml	2010-05-31 06:20:47 UTC (rev 105405)
+++ projects/docs/enterprise/EAP/trunk/5.x/Administration_And_Configuration_Guide/en-US/Transactions.xml	2010-05-31 07:21:52 UTC (rev 105406)
@@ -303,7 +303,7 @@
                         multithreaded transactions. Warning or error messages may be printed from
                         e.g. hibernate or other transaction aware components as a result of the
                         unexpected transaction status change. These should not affect the
-                        transaction outcome. The problem can be minimized by appropriate turning of
+                        transaction outcome. The problem can be minimized by appropriate tuning of
                         the transaction timeout.</para>
         </section>
         <section>

Modified: projects/docs/enterprise/EAP/trunk/5.x/Hibernate_Core_Reference_Guide/en-US/transactions.xml
===================================================================
--- projects/docs/enterprise/EAP/trunk/5.x/Hibernate_Core_Reference_Guide/en-US/transactions.xml	2010-05-31 06:20:47 UTC (rev 105405)
+++ projects/docs/enterprise/EAP/trunk/5.x/Hibernate_Core_Reference_Guide/en-US/transactions.xml	2010-05-31 07:21:52 UTC (rev 105406)
@@ -703,9 +703,9 @@
         <section id="transactions-demarcation-timeout">
             <title>Transaction timeout</title>
 
-            <para>
-                An important feature provided by a managed environment like EJB,
-                that is never provided for non-managed code, is transaction timeout. Transaction
+            <para> 
+                An important feature provided by a managed environment like EJB is
+                transaction timeout, which is never provided in non-managed code. Transaction
                 timeouts ensure that no misbehaving transaction can indefinitely tie up 
                 resources while returning no response to the user. Outside a managed (JTA)
                 environment, Hibernate cannot fully provide this functionality. However,