[
https://issues.apache.org/jira/browse/JCR-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985680#action_12985680
]
Jukka Zitting commented on JCR-2859:
------------------------------------
I would rather not add extra lock tokens to an admin session, since that would
muddy the waters on who is actually owning or holding a lock at a time. Instead
I'd simply give an admin session the right to unlock any open-scoped lock,
regardless of whether it holds the lock token or not.
Note also that the tokens of all open scoped locks are already stored by the
repository in a "locks" file so that they will survive over repository
restarts. But as mentioned above, you probably don't need to worry about the
tokens when implementing this.
> Make open scoped locks recoverable
> ----------------------------------
>
> Key: JCR-2859
> URL: https://issues.apache.org/jira/browse/JCR-2859
> Project: Jackrabbit Content Repository
> Issue Type: New Feature
> Components: locks
> Affects Versions: 2.2.0
> Reporter: Carsten Ziegeler
> Attachments: OpenScopeLockTest.java
>
>
> The lock tokens for open scoped locks are currently tied to the session which
> created the lock. If the session dies (for whatever reason) there is no way
> to recover the lock and unlock the node.
> There is a theoretical way of adding the lock token to another session, but
> in most cases the lock token is not available.
> Fortunately, the spec allows to relax this behaviour and I think it would
> make sense to allow all sessions from the same user to unlock the node - this
> is still in compliance with the spec but would make unlocked locked nodes
> possible in a programmatic way.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
