anchor.diff:  === JCache (JSR-107) Annotations
   
   Since version 4.1, Spring's caching abstraction fully supports the JCache standard
  -annotations: `@CacheResult`, `@CachePut`, `@CacheRemove`, and `@CacheRemoveAll`
  +(JSR-107) annotations: `@CacheResult`, `@CachePut`, `@CacheRemove`, and `@CacheRemoveAll`
   as well as the `@CacheDefaults`, `@CacheKey`, and `@CacheValue` companions.
   You can use these annotations even without migrating your cache store to JSR-107.
   The internal implementation uses Spring's caching abstraction and provides default
  
positive.code: 
  ==== Enabling JSR-107 Support
  
  You need do nothing specific to enable the JSR-107 support alongside Spring's
  declarative annotation support. Both `@EnableCaching` and the
  `cache:annotation-driven` element automatically enable the JCache support
  if both the JSR-107 API and the `spring-context-support` module are present
  in the classpath.
  
  NOTE: Depending on your use case, the choice is basically yours. You can even
  mix and match services by using the JSR-107 API on some and using Spring's own
  annotations on others. However, if these services impact the same caches,
  you should use a consistent and identical key generation implementation.
  
  
  
  
negative.code: support, the caching abstraction allows consistent use of various caching solutions with
  minimal impact on the code.
  
  In Spring Framework 4.1, the cache abstraction was significantly extended with support
  for <<cache-jsr-107,JSR-107 annotations>> and more customization options.
  
  
  
  