[jira] [Commented] (SLING-7792) Resource Resolver should return more than one resolved path if available

["Bertrand Delacretaz (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-7792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16561756#comment-16561756 ] 

Bertrand Delacretaz commented on SLING-7792:
--------------------------------------------

How will the client code select which path to use if you resolve to multiple candidates and return just their paths?

We probably need to see the whole picture of how you intend to use this to understand better, but if there are multiple candidates I think the resolver should provide values such as which one are favorites, or why each candidate is present in the result set, to be able to make a sensible decision about which path to actually use.

Or maybe it's just a question of assigning priorities to the various mapping mechanisms, if their precedence is currently undefined (I' don't know if that's the case).

> Resource Resolver should return more than one resolved path if available
> ------------------------------------------------------------------------
>
>                 Key: SLING-7792
>                 URL: https://issues.apache.org/jira/browse/SLING-7792
>             Project: Sling
>          Issue Type: Bug
>          Components: ResourceResolver
>    Affects Versions: Resource Resolver 1.6.0
>            Reporter: Alex COLLIGNON
>            Priority: Major
>
> The current {{ResourceResolver#map}} methods return a single "path mapped from the (resource) path". However, it is possible than a given path can be mapped to multiple others while using features such as {{sling:alias}} and {{sling:vanityUrl}}.
> In order to support that scenario, it is require to implement new maps method for {{ResourceResolver}} which returns a collection of "resolved path". This collection must contain the resources mapped through {{/etc/map}}, {{sling:alias}} and {{sling:vanityUrl}}.
> The current API suggests to implement a second method to be consistent/symmetric with the existing map operations
> {quote}
> @Nonnull java.util.Collection<java.lang.String> maps(@Nonnull java.lang.String resourcePath)
> @Nonnull java.util.Collection<java.lang.String> maps(@Nonnull javax.servlet.http.HttpServletRequest request, @Nonnull java.lang.String resourcePath)
> {quote}



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