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


A feature I would like to see is a structured way to extend the expiry mechanism, so as to implement domain sensitive expiry.

That is to say, instead of having “expiry” dependent solely upon timestamp and a time-to-live, have it depend upon business logic.

e.g. cached statistics dependent upon a cached dataset. If the dataset is changed the cached statistics are marked to expire.

Perhaps a modular expiry logic that you can plug into net.sf.ehcache.Cache, without having to necessarily extend Cache.


Sourceforge Ticket ID: 1040942 - Opened By: ys2n - 5 Oct 2004 19:49 UTC


Sourceforge Tracker 2009-09-21

Logged In: YES user_id=693320


Ehcache-1.2 has CacheEventListeners. You could register your own listener to add your own business logic.

In your example you could receive notification of an update event. You could achieve “expiry” by then removing the Element.

Regards Greg Luck Comment by: gregluck - 15 Apr 2006 07:14 UTC

Fiona OShea 2009-09-22

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