Why not ? If we're only talking about an in-memory cache (no persistent
cache loader at the far side), then transactions are passed to the cache
in prepare() and commit()/rollback(). Distributed transaction managers
wouldn't help here IMO.
Brian Stansberry wrote:
A different problem is that all the remove() and put() calls
won't be
transactional on the far cache unless you're able to use a distributed
transaction manager.
--
Bela Ban
Lead JGroups / Manager JBoss Clustering Group
JBoss - a division of Red Hat