Uploaded image for project: 'Cache Modules'
  1. Cache Modules
  2. MGNLCACHE-32 Upgrade Ehcache to the latest (2.10.0)
  3. MGNLCACHE-60

Revise EhCacheFactory

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Fixed
    • Icon: Neutral Neutral
    • 5.4
    • None
    • None
    • None

      1. Register cacheManager with context path.
      2. Verify if we still need to load defaults from ehcache-failsafe.xml
        In info.magnolia.module.cache.ehcache.EhCacheFactory#start we do ConfigurationFactory.parseConfiguration(), which is meant to load ehcache default configuration in case we have none. While this might be interesting for users who'd want to have an xml based configuration, this seems counter-intuitive with our tree-based configuration.
        Besides, when there is no specific xml configuration, ehcache fallbacks on its ehcache-failsafe.xml file, which :
      • logs a warning about not finding configuration, which is confusing (since there IS configuration, we just haven't tried loading it yet)
      • only sets up a default cache config and a disk store path - and we always reconfigure both of these.

            rkovarik Roman Kovařík
            gjoseph Magnolia International
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: