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

[Ben Wang (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBCACHE-695?page=all ]

Ben Wang updated JBCACHE-695:
-----------------------------

    Priority: Critical  (was: Major)

> 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();

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira