sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (SLING-7537) Provide a way to get the search paths without login into a resource resolver
Date Thu, 08 Mar 2018 13:21:00 GMT

     [ https://issues.apache.org/jira/browse/SLING-7537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Carsten Ziegeler resolved SLING-7537.
-------------------------------------
    Resolution: Fixed

I've added a new getSearchPath method to the resource resolver factory

> Provide a way to get the search paths without login into a resource resolver
> ----------------------------------------------------------------------------
>
>                 Key: SLING-7537
>                 URL: https://issues.apache.org/jira/browse/SLING-7537
>             Project: Sling
>          Issue Type: New Feature
>          Components: API, ResourceResolver
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>            Priority: Major
>             Fix For: API 2.16.6, Resource Resolver 1.5.38
>
>
> Right now, the only possible way to get the configured search paths for resource resolving
is to actually create a resource resolver (by logging in using a service user). Then the search
paths array can be get from the resolver and the resolver can be closed. This is pretty expensive
for just getting a setting.
> In theory, each resolver could have different search paths; in reality we never went
down this road and I think in fact we can't. There is a lot of code out there, assuming that
each resolver has the same search paths; the resource change listener act in exactly the same
way.
> Therefore I suggest we simply add the search paths either as a service registration property
of the resource resolver factory or as a new method. This makes getting this setting very
easy.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message