You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Angela Schreiber (Jira)" <ji...@apache.org> on 2022/10/20 07:55:00 UTC

[jira] [Created] (OAK-9970) Internal code calls LockManager.isLocked(String)

Angela Schreiber created OAK-9970:
-------------------------------------

             Summary: Internal code calls LockManager.isLocked(String)
                 Key: OAK-9970
                 URL: https://issues.apache.org/jira/browse/OAK-9970
             Project: Jackrabbit Oak
          Issue Type: Improvement
          Components: jcr
            Reporter: Angela Schreiber


similar to OAK-9966 for {{Node.isLocked}} which calls {{LockManager.isLocked(String absPath)}}. This results in the {{Tree}} object to be resolved again from the absolute path, when it was already there for the {{Node}} object.

NOTE: this pattern applies for all other lock related methods. but since JCR locking is not properly implemented, i suggest to focus on the {{Node.isLocked}} method, which is called frequently in code that is just performing regular writes.

cc: [~joerghoh]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)