tim-ehcache should allow selectable inclusion of
net.sf.ehcache.CacheManager.singleton as a root.
--------------------------------------------------------------------------------------------------
Key: CDV-680
URL: https://jira.terracotta.org/jira//browse/CDV-680
Project: Community Development
Issue Type: Bug
Components: Integration Modules
Affects Versions: 2.4.8
Reporter: Alfred Stappenbeck
Assignee: Issue Review Board
This issue comes form a forum posting.
http://forums.terracotta.org/forums/posts/list/904.page
In large coding projects where Ehcache is used often it's dangerous to assume
that CacheManger.getInstance() and CacheManger.create() calls should
automatically get included into terracotta. It's especially hard to manage this
when 3rd party libraries use Ehcache and never intended to have those caches
distributed.
"I'd like to suggest that this be over-ridable in the future. I don't think
it's acceptable for myself or anyone else to have to maintain there own private
branch of tim-ehcache for something so simple. It's pretty hard to enforce that
all your dependencies avoid using the singleton behavior of Ehcache. Regardless
of whether your dependencies are in-house or third party it's to dangerous."
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.terracotta.org/jira//secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
tc-dev mailing list
[email protected]
http://lists.terracotta.org/mailman/listinfo/tc-dev
