• Bug
  • Status: Closed
  • 1 Critical
  • Resolution: Fixed
  • ehcache-core,ehcache-terracotta
  • interfaces
  • Reporter: amiller
  • November 16, 2009
  • 0
  • Watchers: 1
  • December 16, 2011
  • January 26, 2010


Taking a bigger view than EHC-535, there are a bunch of places where classloading happens in Ehcache:

  • Configuration factory classes (almost always classes included in Ehcache, so not too big a deal). This code uses some of the stuff in ClassLoaderUtil
  • TerracottaStoreHelper loading the StoreFactory for either express or custom mode - uses more stuff in ClassLoaderUtil
  • Deserializing objects in DiskStore - this uses a custom object stream that utilizes the TCCL.
  • Deserializing objects in a ClusteredStore

These all use slightly different classloading strategies. Would be nice to consolidate these into something consistent and user configurable. Also might be nice to allow users to associate a classloader with a Cache or CacheManager that would be used for deserialization from disk or clustered stores.


Alex Miller 2009-12-01

Important for some customers to do some more research on how this would best work in osgi.

gluck 2009-12-02

The rather inconsistent and clunky way it is now works. It arrived at this state after a lot of bug reports.

Before closing this JIRA we should review ( I guess with a text search) the old Sourceforge.net bug reports and make sure we don’t break something that is not broken now.

Fiona OShea 2010-01-26

Believe this was resolved in 1.7.2

Kalai Kannaiyan 2010-02-24