From d6ec6f0fe9f50ff2241229a9972a8649ad2dead5 Mon Sep 17 00:00:00 2001 From: Jens Schauder Date: Fri, 1 Oct 2021 09:33:17 +0200 Subject: [PATCH] Remove remark about missing caching API. --- src/docs/asciidoc/integration.adoc | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/src/docs/asciidoc/integration.adoc b/src/docs/asciidoc/integration.adoc index 883acc1786..41d5a0dba8 100644 --- a/src/docs/asciidoc/integration.adoc +++ b/src/docs/asciidoc/integration.adoc @@ -6653,15 +6653,13 @@ invoked every time. === Plugging-in Different Back-end Caches Clearly, there are plenty of caching products out there that you can use as a backing -store. To plug them in, you need to provide a `CacheManager` and a `Cache` implementation, -since, unfortunately, there is no available standard that we can use instead. +store. For those that do not support JSR-107 you need to provide a `CacheManager` and a `Cache` implementation. This may sound harder than it is, since, in practice, the classes tend to be simple https://en.wikipedia.org/wiki/Adapter_pattern[adapters] that map the caching abstraction framework on top of the storage API, as the `ehcache` classes do. Most `CacheManager` classes can use the classes in the `org.springframework.cache.support` package (such as `AbstractCacheManager` which takes care of the boiler-plate code, -leaving only the actual mapping to be completed). We hope that, in time, the libraries -that provide integration with Spring can fill in this small configuration gap. +leaving only the actual mapping to be completed). We hope that, in time, all relevant caches will offer JSR-107 support.