[
https://issues.apache.org/jira/browse/JCR-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977838#action_12977838
]
Cédric Damioli commented on JCR-2859:
-------------------------------------
I tend to agree with Stefan that it's the client responsibility to store lock
tockens.
It's the way I'm managing locks in my applications.
But it may happen some failures (either in the client code or in JR code) that
make the tocken unrecoverable.
Giving the possibility to have some admin feature to cover such cases in IMHO a
very good thing.
Right now, I have to stop the application (which may be very annoying in
production) and modify the locks file by hand.
So a big +1 to Jukka's proposal, if client code is able to have access to such
special sessions.
> 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.
