[ http://issues.apache.org/jira/browse/JCR-429?page=comments#action_12413415 ]
Jukka Zitting commented on JCR-429: ----------------------------------- Merged for 1.0.1 in revision 409614. > Session scoped lock not always removed on Session.logout() > ---------------------------------------------------------- > > Key: JCR-429 > URL: http://issues.apache.org/jira/browse/JCR-429 > Project: Jackrabbit > Type: Bug > Components: locks > Versions: 1.0, 1.0.1, 1.1 > Reporter: Felix Meschberger > Assignee: Stefan Guggisberg > Fix For: 1.0.1 > > Consider the following use case: > Session s = repo.login(...); > Node root = s.getRootNode(); > root.lock(true, true); // session-scoped, deep lock > // modifiy items > // root.isModified() still is true > s.logout(); > To my understanding, the session scoped locks should be removed (unlocked) > and unsaved should be dropped on logout of a session. Unfortunately currently > this is not the case, as the lock implementation gets notified by the > SessionImpl on the logout situation and just calls Node.unlock() on the > lock's node for session scoped locks. This method fails as there are unsaved > changes. Hence after logout, the lock on the session is still there and will > only be gone when the repository is stopped. > -- 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
