This issue was discovered because the CacheFilter class should have had a "cacheConfigurationName" instead of "cacheConfiguration". The actual variable had the correct name and so did the bootstrap file, but the getter/setter pair was wrong; as a result, the default cache config was always used.

• If the cacheConfigurationName isn't set, we will output a warning log statement and fallback to the default (instead of assigning the default value to the variable on initialization)
• If the module can't return a Cache or CacheConfiguration from cacheConfigurationName, we will output an error log statement and disable the filter. (once the configuration is fixed the filter gets reloaded through the magic of CacheModuleLifecycleListener)