jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Cédric Damioli (JIRA) <j...@apache.org>
Subject [jira] Commented: (JCR-2859) Make open scoped locks recoverable
Date Wed, 05 Jan 2011 09:57:48 GMT

    [ https://issues.apache.org/jira/browse/JCR-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977706#action_12977706
] 

Cédric Damioli commented on JCR-2859:
-------------------------------------

It could also be possible to store the lock tocken somewhere (on the locked node ?, on the
node state ?), so that it may be retrieved on demand and set on the current session.

>From my POV, it may be too "dangerous" to allow any session from the same user to unlock
the node.
What if the session which initially locked the node is still alive ?

> 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.


Mime
View raw message