EDIT

Currently ehCache is used in different ways throughout the platform.

• transient entity cache - used by TaxEditor (+ Vaadin?)
• term cache/proxy - should cache terms locally for 120 min but not configured correctly (#10214)
• modelCache (CdmRemotCacheManager) + CacheLoader
• cdmlib-remote/test - springframework - EhCacheManagerFactoryBean
• cdmlib-remote: taxonOqiPmhController - uses springmodules ehcache API (#3408)
• more?

Additionally there are lots of classes for wrapping, adapting, proxying and loading. Many of them in cdmlib-cache but also some in taxeditor (CdmServiceCachingProxy, RemoteInvocationTermCacher, CachedCommonServiceImple).

In some context spring EhCache module is used in others it is not.

Critical is also the handling of EhCacheConfiguration as spring bean which creates the cacheManager and tries to configure the disk storage which does currently not always work as expected. See comments in code.

We should fully implement this after upgrading to ehcache 3.x

Generally there should be 1 cache manager with diskstorage defined in spring configuration depending on application (taxeditor, cdmserver, other).
Also it should depend on instance. If 2 TaxEditor instances are open they should not use the same disk storange. We could use random uuid or startup date to distinguish disk storage.

...