[ http://issues.apache.org/jira/browse/JCR-533?page=comments#action_12427139 ] Stefan Guggisberg commented on JCR-533: ---------------------------------------
paco, please have a look at the javadoc of Node#lock: http://www.day.com/maven/jsr170/javadocs/jcr-1.0/javax/jcr/Node.html#lock(boolean,%20boolean) which states that <quote> [...] If successful, then the property jcr:lockOwner is created and set to the value of Session.getUserID for the current session and the property jcr:lockIsDeep is set to the value passed in as isDeep. These changes are persisted automatically; there is no need to call save. [...] </quote> the lock operation does *not* affect transient space. > 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
