Apply CacheResolver to Spring's caching abstraction [SPR-11490]

[spring-projects-issues]

Stéphane Nicoll opened SPR-11490 and commented

The JSR-107 support (#14250) introduced the concept of CacheResolver that allows to resolve the cache(s) to use at runtime.

Right now, the only reason why the CacheManager is specified is to resolve the cache(s) based on the name(s) provided through the annotation or the cache advice.

The CacheResolver should also be supported by Spring's caching abstraction which would allow to offer a finer level of control of cache resolution.

---

Issue Links:

• Introduce qualifier in @Cacheable for cache manager name [SPR-8696] #13338 Introduce qualifier in @Cacheable for cache manager name
• Support for JSR-107 caching annotations [SPR-9616] #14250 Support for JSR-107 caching annotations
• Provide a @CacheConfig annotation to share class-level customizations [SPR-11316] #15940 Provide a @CacheConfig annotation to share class-level customizations

[spring-projects-issues]

Stéphane Nicoll commented

See snicoll@c20cca1

[spring-projects-issues]

Stéphane Nicoll commented

This has been merged to master. Spring's caching annotations now support the declaration of a CacheResolver as a more flexible alternative to providing the CacheManager to use. A typical use case is to resolve the cache(s) to use dynamically (i.e. with regards to the actual method parameters for instance).

This breaks CachingConfiguration so a CachingConfigurationSupport has been introduced as a better alternative for users.

Note that our handling of the operation has been aligned to some improvements available in the JSR-107 support: all the static metadata about the cache operations are now cached instead of being recomputed at each call.