You could write an SVN-based cache loader - basically a loader that uses SVN to read
contents, generate the cache objects.
You would probably configure this not to use an eviction policy though, since you
don't want objects to expire, rather to trigger an eviction when SVN detects a change.
So you would have to write your own code to listen for changes in SVN, and when a key has
changed, manually evict the key (or all affected keys) from the cache using the
cache.evict() API.
Once the keys are evicted, the next call that comes in for this key will trigger a load
from the CacheLoader, which could then build the object on demand.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4071213#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...