Wrong IllegalStateException for @Cacheable without a cache name [SPR-13081] #17672
Description
Stéphane Nicoll opened SPR-13081 and commented
In 4.1, we've relaxed the structure of caching annotations so that they don't need to refer to any name at all. The name(s) can be provided by a CacheConfig annotation at class level for instance or via a custom CacheResolver that retrieves the cache names using a custom algorithm.
Unfortunately, we are still validating that at least one cache names is specified per operation and we throw an IllegalStateException if that's not the case: it prevent the CacheResolver use case to be used in practice.