You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by "Stefan Guggisberg (JIRA)" <ji...@apache.org> on 2006/08/09 16:58:15 UTC

[jira] Updated: (JCR-533) failing Node.lock() might leave inconsistent transient state

     [ http://issues.apache.org/jira/browse/JCR-533?page=all ]

Stefan Guggisberg updated JCR-533:
----------------------------------

    Summary: failing Node.lock() might leave inconsistent transient state  (was: refresh(false) don't remove falied lock from transiente session)

the real issue at hand is that Node.lock() potentially leaves inconsistent transient state. if the lock operation fails for any reason (e.g. due to lack of privileges) all changes need to be reverted.

> failing Node.lock() might leave inconsistent transient state
> ------------------------------------------------------------
>
>                 Key: JCR-533
>                 URL: http://issues.apache.org/jira/browse/JCR-533
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: locks
>    Affects Versions: 1.0.1
>         Environment: Ubuntu Dapper
>            Reporter: Paco Avila
>         Assigned To: Stefan Guggisberg
>         Attachments: DummyLockAccessDenied.java, MyAccessManagerLockAccessDenied.java
>
>
> When I try to node.lock(true, false) a node and the lock fails due to lak of user privilegies, the lock stay in the user transient session. If a perform a node.refresh(false) the node still is locked in the transient session.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira