[jboss-cvs] JBossAS SVN: r103397 - projects/docs/enterprise/5.0.1/Administration_And_Configuration_Guide/en-US.

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

Author: laubai
Date: 2010-04-01 02:55:43 -0400 (Thu, 01 Apr 2010)
New Revision: 103397

Modified:
   projects/docs/enterprise/5.0.1/Administration_And_Configuration_Guide/en-US/Clustering_Guide_Building_Blocks.xml
Log:
JBPAPP-2644 Replaced JBC with JBoss Cache

Modified: projects/docs/enterprise/5.0.1/Administration_And_Configuration_Guide/en-US/Clustering_Guide_Building_Blocks.xml
===================================================================
--- projects/docs/enterprise/5.0.1/Administration_And_Configuration_Guide/en-US/Clustering_Guide_Building_Blocks.xml	2010-04-01 06:53:42 UTC (rev 103396)
+++ projects/docs/enterprise/5.0.1/Administration_And_Configuration_Guide/en-US/Clustering_Guide_Building_Blocks.xml	2010-04-01 06:55:43 UTC (rev 103397)
@@ -289,33 +289,33 @@
                <listitem>
                  <para><emphasis role="bold">mvcc-entity</emphasis></para>
                  <para>A configuration appropriate for JPA/Hibernate entity/collection 
-               caching that uses JBC's MVCC locking (see notes below).</para>
+               caching that uses JBoss Cache's MVCC locking (see notes below).</para>
                </listitem>
                
                <listitem>
                  <para><emphasis role="bold">optimistic-entity</emphasis></para>
                  <para>A configuration appropriate for JPA/Hibernate entity/collection 
-               caching that uses JBC's optimistic locking (see notes below).
+               caching that uses JBoss Cache's optimistic locking (see notes below).
                </para>
                </listitem>
                
                <listitem>
                  <para><emphasis role="bold">pessimistic-entity</emphasis></para>
                  <para>A configuration appropriate for JPA/Hibernate entity/collection 
-               caching that uses JBC's pessimistic locking (see notes below).
+               caching that uses JBoss Cache's pessimistic locking (see notes below).
                </para>
                </listitem>
                
                <listitem>
                  <para><emphasis role="bold">mvcc-entity-repeatable</emphasis></para>
-                 <para>Same as "mvcc-entity" but uses JBC's REPEATABLE_READ 
+                 <para>Same as "mvcc-entity" but uses JBoss Cache's REPEATABLE_READ 
                isolation level instead of READ_COMMITTED (see notes below).
                </para>
                </listitem>
                
                <listitem>
                  <para><emphasis role="bold">pessimistic-entity-repeatable</emphasis></para>
-                 <para>Same as "pessimistic-entity" but uses JBC's REPEATABLE_READ 
+                 <para>Same as "pessimistic-entity" but uses JBoss Cache's REPEATABLE_READ 
                isolation level instead of READ_COMMITTED (see notes below).
                </para>
                </listitem>
@@ -350,7 +350,7 @@
                which is the least efficient mode. Also requires a full state 
                transfer at startup, which can be expensive. Maintained for 
                backwards compatibility reasons, as a shared cache was the only 
-               option in JBoss 4. Uses JBC's MVCC locking.</para>
+               option in JBoss 4. Uses JBoss Cache's MVCC locking.</para>
                </listitem>
                
                <listitem>
@@ -361,7 +361,7 @@
                which is the least efficient mode. Also requires a full state 
                transfer at startup, which can be expensive. Maintained for 
                backwards compatibility reasons, as a shared cache was the only 
-               option in JBoss 4. Uses JBC's optimistic locking.</para>
+               option in JBoss 4. Uses JBoss Cache's optimistic locking.</para>
                </listitem>
                
                <listitem>
@@ -372,19 +372,19 @@
                which is the least efficient mode. Also requires a full state 
                transfer at startup, which can be expensive. Maintained for 
                backwards compatibility reasons, as a shared cache was the only 
-               option in JBoss 4. Uses JBC's pessimistic locking.</para>
+               option in JBoss 4. Uses JBoss Cache's pessimistic locking.</para>
                </listitem>
                
                <listitem>
                  <para><emphasis role="bold">mvcc-shared-repeatable</emphasis></para>
-                 <para>Same as "mvcc-shared" but uses JBC's REPEATABLE_READ 
+                 <para>Same as "mvcc-shared" but uses JBoss Cache's REPEATABLE_READ 
                isolation level instead of READ_COMMITTED (see notes below).
                </para>
                </listitem>
                
                <listitem>
                  <para><emphasis role="bold">pessimistic-shared-repeatable</emphasis></para>
-                 <para>Same as "pessimistic-shared" but uses JBC's REPEATABLE_READ 
+                 <para>Same as "pessimistic-shared" but uses JBoss Cache's REPEATABLE_READ 
                isolation level instead of READ_COMMITTED. (see notes below).
                </para>
                </listitem>