[
https://issues.apache.org/jira/browse/SLING-790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-790.
-----------------------------------
Resolution: Fixed
Implemented support for path mangling if the mapped path is actually an URL in
Rev. 737694.
This revision also extends the unit tests and verifies the servlet context
paths are also properly prepended.
> JcrResourceResolver2.map method does not apply namespace mangling and context
> path prefix to mapped URL
> -------------------------------------------------------------------------------------------------------
>
> Key: SLING-790
> URL: https://issues.apache.org/jira/browse/SLING-790
> Project: Sling
> Issue Type: Bug
> Components: JCR Resource
> Affects Versions: JCR Resource 2.0.4
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: JCR Resource 2.0.4
>
>
> If a resource, say "/content/some/page/jcr:content" is mapped to an absolute
> URL using the mapping rule
> /content/ --> http://host/
> it is returned as
> http://host/some/page/jcr:content
> whereas it would be expected to be returned as
> http://host/some/page/_jcr_content
> Similarly, given that Sling would be launched in the "/rooted" context, the
> mapped result as above would be expected as
> http://host/root/some/page/_jcr_content
> That is the "/rooted" context is expected to be prepended.
> Namespace mangling and context prefixing work for simple path mappings where
> not an absolute URL is created.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
