Angela Schreiber created OAK-9868:
-------------------------------------
Summary: Introduce interface to extract tree from users
Key: OAK-9868
URL: https://issues.apache.org/jira/browse/OAK-9868
Project: Jackrabbit Oak
Issue Type: Improvement
Components: auth-external, core, security-spi
Reporter: Angela Schreiber
Assignee: Angela Schreiber
while working on OAK-9803 it struck me that there are several places in the oak
security code base where a tree object needs to be retrieved from a given
user/group, which according to the API contract only has a {{getPath()}} method
returning a JCR path.
Since the default implementation is backed by a tree object, it would in
certain cases (same content session being used to retrieve the {{User}} and the
{{Root}}) be possible (and likely better from a performance point of view) if
there was an option to access the tree instead of traversing the hierarchy
again to build it from the path.
cc: [~joerghoh], fyi
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
