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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Resource Resolver 1.6.0
• Fix Version/s: API 2.18.4, Resource Resolver 1.6.6
• Component/s: API, ResourceResolver
• Assignee: Robert Munteanu
• Reporter: Alex Collignon
• Created: 30/Jul/18 09:09
• Updated: 20/Jan/23 14:18
• Resolved: 17/Aug/18 14:11

Description

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

@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)

Issue Links

• relates to: SLING-11757 resource resolver: pathless URL in vanity path causes NPE in ResourceMapperImpl.apply()
• relates to: SLING-5773 NonExistingResource.getParent() must consider the resource resolver mapping
• links to: GitHub Pull Request #6
• links to: GitHub Pull Request #9