[
https://issues.apache.org/jira/browse/JCR-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977797#action_12977797
]
Stefan Guggisberg commented on JCR-2859:
----------------------------------------
> There is a theoretical way of adding the lock token to another session, but
> in most cases the lock token is not available.
why? if a client does create an open-scoped lock (he has to do so explicitly)
he's responsible for persisting the lock token
for future use. if the client doesn't want to do that he should use
session-scoped locks instead.
> There is no API in JCR to get the lock token
LockManager.lock(...) returns a Lock instance => Lock.getLockToken()
> I think it would make sense to allow all sessions from the same user to
> unlock the node
-1, i'd consider this rather a hack; the current behavior is IMO correct.
> 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
>
> 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.
