You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2018/03/19 06:20:00 UTC
[jira] [Closed] (SLING-7537) Provide a way to get the search paths
without login into a resource resolver
[ https://issues.apache.org/jira/browse/SLING-7537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler closed SLING-7537.
-----------------------------------
> 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.18.0, 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)