We would like to use the JBossCache for replicating data across machines, however we don't want all the data to be replicated. It would be really nice if we could set a "isCacheable" boolean on objects we would like to be cached.

I think the only way to prevent data from replicated is to prevent hibernate from adding the objects into its second level cache. However objects are immediately added into the second level cache when doSave() is called in the Session. At the moment, we have all classes & collections cached and feel there is too much unnecessary data being distributed on the network. Is there something else that can be tried to have a selective-object caching?

Dean Mao
InterContinental Hotels Group

Does the new CacheMode in HB3.0 help? (It should do...)

Otherwise, in HB3, you could enable hibernate.cache.use_structured_cache_entries, and write a Cache implementation that wraps JBossCache and intercepts put(), inspects the property value Map.

If that is too messy, or can't work, I'm receptive to adding some callback.

I had a brief spasm of insight while looking through the hibernate code. Would it be possible to extend the TreeCacheProvider and TreeCache classes, and then override the TreeCache.put() and TreeCache.get() to selectively decide what objects go into the cache? This would be a bit hackish, but would it work?

I assume this is what you mean by "writing a Cache implementation that wraps JBossCache and intercepts put()" ?

Dean
InterContinental Hotels Group