You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Paco Avila (JIRA)" <ji...@apache.org> on 2006/08/09 18:59:16 UTC
[jira] Commented: (JCR-533) failing Node.lock() might leave
inconsistent transient state
[ http://issues.apache.org/jira/browse/JCR-533?page=comments#action_12426970 ]
Paco Avila commented on JCR-533:
--------------------------------
Ok, Node.lock() when fails don't save state on transient session. But why? When I try a node modification on a node where I have no permissions and perform a Node.save(), it throws a AccessDeniedException and I have to make a session.refresh(false) because the modification is in my transient session. Why in the case of lock it is different?
> 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