[
https://issues.apache.org/jira/browse/JCR-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-2341:
-------------------------------
Status: Open (was: Patch Available)
Cancelling the patch as there are concerns about the design.
We can apply this patch if there's a strong need for this fix and no easy
alternative, but then we'd need to add appropriate warnings to the
getNodeState() javadoc and open a new issue to remind us about the required
refactoring.
> 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.
