From 6e30b565b7ec7e409d40985b72a8ab98477ce84b Mon Sep 17 00:00:00 2001 From: "Kevin W. Sutter" Date: Thu, 1 Mar 2007 17:44:44 +0000 Subject: [PATCH] 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. git-svn-id: https://svn.apache.org/repos/asf/incubator/openjpa/trunk@513417 13f79535-47bb-0310-9956-ffa450edef68 --- openjpa-project/src/doc/manual/ref_guide_caching.xml | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/openjpa-project/src/doc/manual/ref_guide_caching.xml b/openjpa-project/src/doc/manual/ref_guide_caching.xml index ba1ac23bd..df0536096 100644 --- a/openjpa-project/src/doc/manual/ref_guide_caching.xml +++ b/openjpa-project/src/doc/manual/ref_guide_caching.xml @@ -572,10 +572,9 @@ qcache.evict (q); 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. Queries can also be pinned and unpinned through the