Hello,

I could not find any documentation that describes the behavior of data mutating 
operations wrt transactions when executed against TRANSACTIONAL caches. 

Specifically, I'd like to know whether or not the mutators start implicit 
transactions and if so, how do I configure the properties of such transactions 
(concurrency, isolation, etc). Do I use the global TransactionConfiguration 
class to configure the defaults? In my case, some of my caches require 
different (non-default) transactional semantics. What are my options in this 
case? I can indeed wrap every mutator call into an explicit transaction. Any 
other options?

I feel it would make the use of the API a bit simpler if it were possible to 
configure the transactional properties on the CacheConfiguration class directly 
rather than for each explicitly started transaction.

Thanks
Andrey
                                          

Reply via email to