anchor.diff:  Sometimes, when switching environments or doing testing, you might have cache
   declarations without having an actual backing cache configured. As this is an invalid
   configuration, an exception is thrown at runtime, since the caching infrastructure
  -is unable to find a suitable store. In situations like this, rather then removing the
  +is unable to find a suitable store. In situations like this, rather than removing the
   cache declarations (which can prove tedious), you can wire in a simple dummy cache that
   performs no caching -- that is, it forces the cached methods to be executed every time.
   The following example shows how to do so:
  
positive.code: 
  
  This option comes in handy when an entire cache region needs to be cleared out. Rather
  then evicting each entry (which would take a long time, since it is inefficient), all the
  entries are removed in one operation, as the preceding example shows. Note that the framework ignores
  any key specified in this scenario as it does not apply (the entire cache is evicted, not
  only one entry).
  
negative.code: 	}
  ----
  
  If simple periodic scheduling is not expressive enough, you can provide a cron expression.
  For example, the following executes only on weekdays:
  
  [source,java,indent=0]
  