[jboss-jira] [JBoss JIRA] Updated: (JBCACHE-173) Locking model when pojo is multiple referenced

[Ben Wang (JIRA)]

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

Ben Wang updated JBCACHE-173:
-----------------------------

    Fix Version/s: 2.0.0
                       (was: POJOCache)

> Locking model when pojo is multiple referenced
> ----------------------------------------------
>
>                 Key: JBCACHE-173
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-173
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: PojoCache
>    Affects Versions: POJOCache
>            Reporter: Ben Wang
>         Assigned To: Ben Wang
>             Fix For: 2.0.0
>
>   Original Estimate: 2 weeks
>  Remaining Estimate: 2 weeks
>
> Under the new PojoCache, when a pojo is multiple referenced (let's say a pojo, Joe), it will be located under JBOSS_INTERANL node while leaving the original with a fqn/id reference. 
> In terms of locking, there are various implications.
> 1. If we are modifying Joe under a tx context directly, the locking will be done under the JBoss_INTERNAL node. As a result, consistency is warranted.
> 2. If Joe is part of a sub-object, say, a UserState object that has a Person Joe reference. Then, a tx context under that UserState obejct is not locking on Joe (since it has been moved to under JBOSS_INTERNAL, and therefore not under the same fqn sub-tree).

-- 
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