Node not locked after upgrade to Jackrabbit 2.2.9
-------------------------------------------------
Key: JCR-3155
URL: https://issues.apache.org/jira/browse/JCR-3155
Project: Jackrabbit Content Repository
Issue Type: Bug
Components: jackrabbit-core
Affects Versions: 2.2.9
Reporter: Sascha Theves
Fix For: 2.2.10
Lock a node in Jackrabbit 1.6.2 with node.lock(true, false). That is a deep
lock, not session-scoped.
Then upgrade to Jackrabbit 2.2.9 and check the node with node.isLocked.
Now node.isLocked() returns false (wrong!) and
node.getProperty("jcr:lockOwner") is set. That is an inconsistent node state.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
