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

2018-08-17 Thread Robert Munteanu (JIRA)


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

Robert Munteanu resolved SLING-7792.

Resolution: Fixed

Fixed edge case in [sling-org-apache-sling-resourceresolver commit 
9ff4836|https://github.com/apache/sling-org-apache-sling-resourceresolver/commit/9ff4836]


> 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: API, ResourceResolver
>Affects Versions: Resource Resolver 1.6.0
>Reporter: Alex COLLIGNON
>Assignee: Robert Munteanu
>Priority: Major
> Fix For: API 2.18.4, Resource Resolver 1.6.6
>
>  Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> 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 maps(@Nonnull 
> java.lang.String resourcePath)
> @Nonnull java.util.Collection maps(@Nonnull 
> javax.servlet.http.HttpServletRequest request, @Nonnull java.lang.String 
> resourcePath)
> {quote}



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


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

2018-08-17 Thread Robert Munteanu (JIRA)


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

Robert Munteanu resolved SLING-7792.

Resolution: Fixed

Fixed, with

* [sling-org-apache-sling-api commit 
64e2a90|https://github.com/apache/sling-org-apache-sling-api/commit/64e2a90]
* [sling-org-apache-sling-resourceresolver commit 
bdfa9e3|https://github.com/apache/sling-org-apache-sling-resourceresolver/commit/bdfa9e3]
* [sling-org-apache-sling-resourceresolver commit 
b01bea8|https://github.com/apache/sling-org-apache-sling-resourceresolver/commit/b01bea8]
* [sling-org-apache-sling-resourceresolver commit 
def05b6|https://github.com/apache/sling-org-apache-sling-resourceresolver/commit/def05b6]

> 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: API, ResourceResolver
>Affects Versions: Resource Resolver 1.6.0
>Reporter: Alex COLLIGNON
>Assignee: Robert Munteanu
>Priority: Major
> Fix For: API 2.18.4, Resource Resolver 1.6.6
>
>  Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> 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 maps(@Nonnull 
> java.lang.String resourcePath)
> @Nonnull java.util.Collection maps(@Nonnull 
> javax.servlet.http.HttpServletRequest request, @Nonnull java.lang.String 
> resourcePath)
> {quote}



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