EHC ❯ CacheManager with no name should use default CacheManager when locating clustered caches

• Type: Task
• Status: Closed
• Priority: 1 Critical
• Resolution: Fixed
• Component/s: ehcache-core
• Labels:

• Assignee: amiller
• Reporter: amiller
• Created: September 22, 2009
• Votes: 0
• Watchers: 0
• Updated:

  July 27, 2012
• Resolved:

  September 24, 2009

Description

Need to add a test for this common scenario where CacheManagers are not named - the clustered identity mechanism should deal with this scenario and properly cluster caches in the default CacheManager space.

Comments

Alex Miller 2009-09-24

Think this is handled but need to add a test for a CacheManager with no name.

Alex Miller 2009-09-24

Apparently this is busted - make it work!

Alex Miller 2009-09-24

Added call to CacheManager.isNamed() and I’m now checking that flag in TerracottaStoreFactory.create() and if no name is defined, a default (“__DEFAULT__”) is used instead.