Yes, you can suppress the cache loader from writing by setting
ignoreModifications to true in your cache loader cfg.
And yes, in this case wasRemovedInTx() will prevent the value from being loaded
from the cache loader - this is an optimisation since in MOST cache loaders
this would result in a
Hi Manik,
thank you for your response. This indeed makes sense, though I forgot to
mention that our custom CacheLoader is one-way; it does not write any values
back to the store.
Is there a way I can configure JBC so it does not try to persist the data using
the CacheLoader?
Regarding locks,
Looking at your scenario I think this is expected behaviour.
cache.remove() will remove the node and all it's children. When you use a
cache loader, this behaviour is passed on to the cache loader too.
So when you do cache.remove("/a") this will remove /a and all its children both
in memory an
