[
https://issues.apache.org/jira/browse/JCR-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12762112#action_12762112
]
Claus Köll commented on JCR-2341:
---------------------------------
you are both right ... its really no a good idea to expose such informations to
the public api.
but i don't know how to solve that problem ... i will look at it maybe i will
find a way
greets
claus
> 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.
