anchor.diff:     `JCacheConfiguration.Builder.supportOnlineListenerAttachment`. If no listeners are needed, which is most
      often the case, cache2k switches to a faster internal processing mode.
   
  -To enable full JCache compliance by default via the XML configuration, use these defaults
  -in the setup:
  +To enable full JCache compliance by default via the XML configuration, use these defaults in the setup:
   
   [source,xml]
   ----
  
positive.code: 
  ==== Optimizations and Semantic Differences
  
  WARNING: In case in the creation context of a JCache a cache2k configuration is present, the created JCache
  has different semantics then those defined in the JCache specification. The reason is, because cache2k has
  different defaults, which are optimized during performance if a specific feature ore semantic is not needed.
  The following sections explains the differences and how to switch back to the standard behavior,
  if this is needed.
  
  Expiry:: With pure JCache configuration the expiry is set to sharp expiry by default for maximum compatiblity. When the
     cache2k configuration is used, sharp expiry is off and need to be enabled explicitly.
  
negative.code: </cache2k>
  ----
  
  There are more optimizations in cache2k happening transparently, e.g. when a expiry policy with a static
  setting is detected. For this reason avoid using a custom expiry policy class.
  
  ==== Merging of JCache and cache2k Configuration
  
  The JCache configuration and the cache2k configuration may have settings that control the same
  