[ https://issues.apache.org/jira/browse/SLING-3206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13806073#comment-13806073 ]
Gilles Knobloch commented on SLING-3206: ---------------------------------------- I did not yet had a look at how vanity paths are evaluated (sorry), but in context of SLING-2986, I would need the vanity path to be set of the merged resource. For instance, if you have {{sling:vanityPath}} = {{/mypath}} set on {{/libs/my/resource}}, the vanity path should actually go to {{/merge/my/resource}}. I could of course use request filters to redirect, but then the URL would change. I'd prefer if it's integrated in the vanity path evaluation. > Create an API to handle resource vanity paths > --------------------------------------------- > > Key: SLING-3206 > URL: https://issues.apache.org/jira/browse/SLING-3206 > Project: Sling > Issue Type: Improvement > Components: API > Reporter: Carsten Ziegeler > > Right now vanity path handling is complicated, it would be nice to have a > central API which allows to set a vanity path for a resource and to query if > a vanity path for a resource is set. > Maybe a method getting all vanity paths back could be added as well. > The implementation would directly write into the mapping structure in the > resource tree. For the query part, it would mark its own entries to easily > identify them in contrast to entries created by other means -- This message was sent by Atlassian JIRA (v6.1#6144)