anchor.diff:  === Configuring caching using Java configuration
   Spring Cloud AWS also support the cache configuration with Java configuration classes. On any `Configuration` class,
   the caching can be configured using the `org.springframework.cloud.aws.cache.config.annotation.EnableElastiCache`
  -annotation provided by Spring Cloud AWS. The next example shows a configuration of two cache clusters using the `lusters`
  -attribute.
  -
  -[source,java,indent=0]
  -----
  -
  -@EnableElastiCache(clusters = {"firstCache", "secondCache"})
  +annotation provided by Spring Cloud AWS. The next example shows a configuration of two cache clusters.
  +
  +[source,java,indent=0]
  +----
  +
  +@EnableElastiCache({@CacheClusterConfig(name = "firstCache"), @CacheClusterConfig(name = "secondCache")})
   public class ApplicationConfiguration {
   }
   ----
   
  -IMPORTANT: If you leave the `clusters` attribute empty, then all the caches inside your CloudFormation stack (if available)
  +IMPORTANT: If you leave the `value` attribute empty, then all the caches inside your CloudFormation stack (if available)
   will be configured automatically.
  +
  +==== Configuring expiry time for caches
  +The java configuration also allows to configure the expiry time for the caches. This can be done for all
  +caches using the `defaultExpiration` attribute as show in the example below.
  +
  +[source,java,indent=0]
  +----
  +
  +@EnableElastiCache(defaultExpiration = 23)
  +public class ApplicationConfiguration {
  +}
  +----
  +
  +or on a cache level using the `@CacheClusterConfig` annotations expiration attribute as shown below.
  +
  +[source,java,indent=0]
  +----
  +
  +@EnableElastiCache({@CacheClusterConfig(name = "firstCache", expiration = 23), @CacheClusterConfig(name = "secondCache", expiration = 42)})
  +public class ApplicationConfiguration {
  +}
  +----
  +
   
   === Configuring caching in Spring Boot
   The caches will automatically be configured in Spring Boot without any explicit configuration property.
  
positive.code: inside the cache manager.
  
  The example below demonstrates a configuration example that contains a pre-configured cache with an `cache-ref` element
  (which might be a local cache), a `cache` with an explicit address (that is probably hosted outside ElastiCache) and
  a `cache-cluster` configuration.
  
  [source,xml,indent=0]
  ----
  <beans ...>
  	<aws-cache:cache-manager id="cacheManager">
  		<aws-cache:cache-ref ref="memcached" />
  		<aws-cache:cache address="someLocalServer:4321" name="memc" />
  		<aws-cache:cache-cluster name="SimpleCache"/>
  	</aws-cache:cache-manager>
  </beans>
  
negative.code: to support an expiry time. The Spring Cloud AWS cache configuration supports the expiry time setting per cache. The
  expiry time will be passed to the memcached service.
  
  The `cache-cluster` element accepts an expiration attribute that defines the expiration time in seconds.
  No configured values implies that there is an infinite expiration time.
  
  [source,xml,indent=0]
  ----
  <beans>
  	<aws-cache:cache-manager>
  		<aws-cache:cache-cluster expiration="10000" name="CacheCluster" />
  	</aws-cache:cache-manager>
  </beans>
  