[
https://issues.apache.org/jira/browse/SLING-9672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17179654#comment-17179654
]
Robert Munteanu commented on SLING-9672:
----------------------------------------
[~angela] - yes, that is also an option. I'm reluctant to add it since it would
increase the API surface from 4 to 6 methods, so I will keep it as a fallback
in case I discovery breakages due to the behaviour change.
> Expose vanity paths from ResourceMapper.getAllMappings()
> --------------------------------------------------------
>
> Key: SLING-9672
> URL: https://issues.apache.org/jira/browse/SLING-9672
> Project: Sling
> Issue Type: Improvement
> Components: ResourceResolver
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Priority: Major
> Fix For: Resource Resolver 1.6.18
>
>
> With SLING-9622 we have removed all the complexity of knowing about aliases,
> vanity paths, mappings from the auth core bundle. However, the ResourceMapper
> does not expose vanity paths.
> We can include this information and return more paths from
> ResourceMapper.getAllMappings, as long as we make sure that we do not alter
> the way the ResourceMapper.getMapping / ResourceResolver.map() methods work.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
