[ https://issues.apache.org/jira/browse/SLING-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler resolved SLING-1005. ------------------------------------- Resolution: Fixed Setting this to resolved to not block the release. > JcrResourceResolver2.map should consider request path info for mapping > ---------------------------------------------------------------------- > > Key: SLING-1005 > URL: https://issues.apache.org/jira/browse/SLING-1005 > Project: Sling > Issue Type: Bug > Components: JCR > Affects Versions: JCR Resource 2.0.4 > Reporter: Felix Meschberger > Assignee: Felix Meschberger > Fix For: JCR Resource 2.0.6 > > > The currently the JcrResourceResolver2.map method applies the following basic > algorithm for reverse mapping a resource path: > * Resolve resource cutting of resource path info. E.g. /content/page.html > would give a resource /content/page and resource path info .html > * Resolve alias names of the resource (if any) > * Apply mapping on the resource > * Append resource path Info > This is probably wrong, since any incoming mapping / --> /content/page.html > would not be revers mapped from /content/page.html to / due to the resource > path info not bein appended after resolve the resource and alias names. > The fix is to append the resource path info *before* applying the mappings. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.