[jboss-user] [JBossCache] - Re: locking & CacheSPI

2008-03-12 Thread [EMAIL PROTECTED]
Use a Transaction Manager (see the user guide for how to configure one) and start a user transaction before your cache operations (reads, writes). And then commit your transaction. The cache will participate in the transaction and treat all operations as scoped to the same ongoing transaction.

[jboss-user] [JBossCache] - Re: locking & CacheSPI

2008-03-11 Thread nnnnn
Right, that's what I would like to do. But how do I do that from application code without having my app code operate in an Interceptor? Am I missing something easy? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135763#4135763 Reply to the post : http://w

[jboss-user] [JBossCache] - Re: locking & CacheSPI

2008-03-10 Thread mircea.markus
anonymous wrote : When our application decides to write to the cache, it needs to check what's already at the node that's there, and then depending on what it finds, it may choose to put the new object in the cache in the same node, or it may decide not to. It's important that a different thread