[MGNLCACHE-68] Set explicit name for Ehcache CacheManager Created: 12/Aug/14  Updated: 05/Feb/15  Resolved: 13/Aug/14

Status: Closed
Project: Cache Modules
Component/s: configuration
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Magnolia International Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
supersession
is superseded by MGNLCACHE-60 Revise EhCacheFactory Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)

 Description   

The net.sf.ehcache.CacheManager instead we configure in EhCacheFactory is currently unnamed. Naming would help identifying it in tools (monitoring, ...) and ensure its uniqueness (if we don't specify a name, EhCache calls it "default", which could then possibly also clash with other tools)



 Comments   
Comment by Magnolia International [ 13/Aug/14 ]

Pushed to feature/cache-arbitrary-objects-2 branch.

Generated at Sun Feb 11 23:51:53 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.