-
1. Re: In memorry persistence with periodical saving to database
galder.zamarreno Feb 7, 2012 4:15 AM (in response to niknik77771)1 of 1 people found this helpfulRe 1. Hmmm. not that I'm aware of, but you could build such capability very easily with a cache listener that listens for @CacheEntryRemoved events. In the listener code, you could check if the particular key being deleted matches the one you wanna keep always in memory, and if it does, send an exception or abort the execution (you'd do this check when event.isPre() is true). More info on listeners: https://docs.jboss.org/author/display/ISPN/Listeners+and+Notifications
Re 2. Periodic flushing to backend stores is not yet implemented, see https://issues.jboss.org/browse/ISPN-328 - fancy helping us implement it?
-
2. Re: In memorry persistence with periodical saving to database
niknik77771 Feb 7, 2012 4:50 PM (in response to galder.zamarreno)Thank you for reply
1. Does event provide value, that should be deleted? If so event listener can update cache.
2. Periodic flushing is simple with concurrent api.