[
http://jira.jboss.com/jira/browse/JBCACHE-717?page=all ]
Ben Wang resolved JBCACHE-717.
------------------------------
Resolution: Done
Since there is not a good way to check whether this is Collection operation or not, I am
checking 1) whether it is JBossInternal node, and 2) whether it has more 3 fqn levels. It
is a bit ad hoc.
PojoCache to lock parent node during transaction
------------------------------------------------
Key: JBCACHE-717
URL:
http://jira.jboss.com/jira/browse/JBCACHE-717
Project: JBoss Cache
Issue Type: Task
Security Level: Public(Everyone can see)
Components: PojoCache
Reporter: Ben Wang
Assigned To: Ben Wang
Fix For: 2.0.0
In current 2.0 implementation, the TxLockInterceptor (applies for attach and detach)
locks only the current node. This is not adequate, however, when the POJO is Collection.
In that case, we will try to do another attach to the children (e.g., col/0, and col/1).
In this case, we should lock the parent (/col) such that no other Collection operation can
be applied.
--
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