[jboss-jira] [JBoss JIRA] Updated: (JBCACHE-695) PojoCache transaction context has limitation for in-memory rollbakck

PojoCache transaction context has limitation for in-memory rollbakck -------------------------------------------------------------------- Key: JBCACHE-695 URL: http://jira.jboss.com/jira/browse/JBCACHE-695 Project: JBoss Cache Issue Type: Bug Security Level: Public(Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Priority: Critical Fix For: 2.0.0 Currently PojoCache supports transaction rollback. For instance, cache.attach(id, pojo); is transactional even if there is no user transaction. However, with user transaction, tx.begin(); cache.attach(id, pojo); pojo.setAge(20); tx.rollback(); the replication is rollbacked but the in-memory copy is not, e.g., pojo.getAge() == 20. There is a workaround if you are using transaction by yourself: // Just make sure this one succeeds first. tx.begin(); cache.attach(id, pojo); tx.commit(); // All subsquent field update will be transactional then. tx.begin(); pojo.setAge(20); tx.rollback();