[
https://issues.apache.org/jira/browse/JCR-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996856#comment-12996856
]
Janandith Uditha Jayawardena edited comment on JCR-2859 at 2/19/11 8:42 PM:
----------------------------------------------------------------------------
Attached a patch. If the session is an admin session and lock is open scoped
the session will be
the lock holder so it can be unlocked.
Modified AbstractLockTest and OpenScopedLockTest to work with
new feature.
was (Author: janandith):
If the session is an admin session and lock is open scoped the session will
be
the lock holder so it can be unlocked.
Modified AbstractLockTest and OpenScopedLockTest to work with
new feature.
> 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: JCR-2859.patch, 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
