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/07 10:24:15 UTC
[jira] Updated: (JCR-533) refresh(false) don't remove falied lock
from transiente session
[ http://issues.apache.org/jira/browse/JCR-533?page=all ]
Paco Avila updated JCR-533:
---------------------------
Attachment: DummyLockAccessDenied.java
Test program
> refresh(false) don't remove falied lock from transiente session
> ---------------------------------------------------------------
>
> 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
> 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