[
https://issues.apache.org/jira/browse/JCR-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Janandith Uditha Jayawardena updated JCR-2859:
----------------------------------------------
Attachment: OpenScopeLockTest.java
Attached a test case for the scenario described in this JIRA,
I'm working on a patch.
The solution I'm working on is as follows,
1. Store lock tokens when a node is locked using LockManager.
2. Add the locked tokens from the stored location to the session when session
is created if principal is AdminPrincipal.
3. Remove the lock token from the store when the node is unlocked using admin
session.
I would like to know the following,
1. Will there be any consequences in above solution ?.
2. What is the best place to store the lock tokens ? . Is it in a node like ex:
/locktokens or a file)
3. Any improvements, suggestions ?.
> 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.
