[MGNLCACHE-66] Explicitly prevent an Ehcache named "default" Created: 29/Jul/14  Updated: 05/Feb/15  Resolved: 13/Aug/14

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

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

Issue Links:
Relates
relates to MGNLCACHE-32 Upgrade Ehcache to the latest (2.10.0) Closed
relates to MGNLCACHE-55 Caching arbitrary objects 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   

Because Ehcache tends to be confusing (to me, anyway) about the differences between "defaultCacheConfiguration" and "the default cache", I'd rather prevent the usage of an actual cache named "default". It'll also help keep the configuration a tad simpler for multiple caches (see MGNLCACHE-55).



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

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

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