jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Guggisberg (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-2341) LockManager should use NodeState of the Node itself to remove the PropertyState on unlock
Date Fri, 02 Oct 2009 08:35:23 GMT

    [ https://issues.apache.org/jira/browse/JCR-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761508#action_12761508
] 

Stefan Guggisberg commented on JCR-2341:
----------------------------------------

> ... The only thing is that i had to change the getNodeState method in NodeImpl to public
...

can this be avoided? i'd be rather reluctant to expose NodeState to api client... 

> LockManager should use NodeState of the Node itself to remove the PropertyState on unlock
> -----------------------------------------------------------------------------------------
>
>                 Key: JCR-2341
>                 URL: https://issues.apache.org/jira/browse/JCR-2341
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: 1.6.0
>            Reporter: Claus Köll
>            Assignee: Claus Köll
>             Fix For: 1.6.1
>
>         Attachments: JCR-2341.patch
>
>
> If you try to unlock and remove a node the NodeState can be run out of sync between the
two operations.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message