Remove remark about missing caching API.
This commit is contained in:
parent
7311ae19be
commit
d6ec6f0fe9
|
@ -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.
|
||||
|
||||
|
||||
|
||||
|
|
Loading…
Reference in New Issue