• Bug
  • Status: Closed
  • Resolution: Fixed
  • drb
  • Reporter: sourceforgetracker
  • September 21, 2009
  • 0
  • Watchers: 0
  • September 22, 2009
  • September 22, 2009


I’m using EHCache 1.3.0-beta. In net.sf.ehcache.CacheManager.addCacheNoCheck(), the defaultCache is cloned. However, in the implementation of this clone() operation, the member variable “CacheConfiguration configuration” is left untouched. Later, the cache that is thus cloned is given a new name through the setName() method. As it forwards this to the configuration member, ALL cloned caches get the new name. This seems to me not correct. I see that this new member has been added after version 1.2.4.

Sourceforge Ticket ID: 1704257 - Opened By: erikvoorbraak - 20 Apr 2007 11:48 UTC


Fiona OShea 2009-09-22

Re-opening so that I can properly close out these issues and have correct Resolution status in Jira