openjpa-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kwsut...@apache.org
Subject svn commit: r513417 - /incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_caching.xml
Date Thu, 01 Mar 2007 17:44:45 GMT
Author: kwsutter
Date: Thu Mar  1 09:44:44 2007
New Revision: 513417

URL: http://svn.apache.org/viewvc?view=rev&rev=513417
Log:
While looking at how the Caches are supposed to work, I found this reference to Tangosol's
cache.  And, since we don't ship the plugins for the third-party caches, I changed the wording
in the manual.

Modified:
    incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_caching.xml

Modified: incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_caching.xml
URL: http://svn.apache.org/viewvc/incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_caching.xml?view=diff&rev=513417&r1=513416&r2=513417
==============================================================================
--- incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_caching.xml (original)
+++ incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_caching.xml Thu Mar 
1 09:44:44 2007
@@ -572,10 +572,9 @@
             <para>
 When using one of OpenJPA's distributed cache implementations, it is necessary
 to perform this in every JVM - the change notification is not propagated
-automatically. When using a coherent cache implementation such as OpenJPA's
-Tangosol cache implementation, it is not necessary to do this in every JVM
-(although it won't hurt to do so), as the cache results are stored directly in
-the coherent cache.
+automatically. When using a third-party coherent caching solution,
+it is not necessary to do this in every JVM (although it won't hurt to do so),
+as the cache results are stored directly in the coherent cache.
             </para>
             <para>
 Queries can also be pinned and unpinned through the <classname>



Mime
View raw message