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
This commit is contained in:
Kevin W. Sutter 2007-03-01 17:44:44 +00:00
parent af1796f17c
commit 6e30b565b7
1 changed files with 3 additions and 4 deletions

View File

@ -572,10 +572,9 @@ qcache.evict (q);
<para> <para>
When using one of OpenJPA's distributed cache implementations, it is necessary When using one of OpenJPA's distributed cache implementations, it is necessary
to perform this in every JVM - the change notification is not propagated to perform this in every JVM - the change notification is not propagated
automatically. When using a coherent cache implementation such as OpenJPA's automatically. When using a third-party coherent caching solution,
Tangosol cache implementation, it is not necessary to do this in every JVM it is not necessary to do this in every JVM (although it won't hurt to do so),
(although it won't hurt to do so), as the cache results are stored directly in as the cache results are stored directly in the coherent cache.
the coherent cache.
</para> </para>
<para> <para>
Queries can also be pinned and unpinned through the <classname> Queries can also be pinned and unpinned through the <classname>