[
https://issues.apache.org/jira/browse/SLING-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Klimetschek resolved SLING-696.
-----------------------------------------
Resolution: Won't Fix
I think this can be closed as wontfix as the proper mechanisms are already
present:
1) simple servlet api style: request.getContextPath() + path
2) aware of sling mappings (in new jcrresourcersolver):
request.getResource().getResourceResolver().map(request, path)
> Add externalizeHref() to SlingHttpServletResponse
> -------------------------------------------------
>
> Key: SLING-696
> URL: https://issues.apache.org/jira/browse/SLING-696
> Project: Sling
> Issue Type: New Feature
> Components: API, Engine
> Reporter: Alexander Klimetschek
>
> A SlingHttpServletResponse.externalizeHref() method, that correctly maps a
> JCR resource path back to the URL that has to be used externally to access
> that resource, would be very helpful for use in HTML rendering scripts and
> servlets.
> The implementation would need to:
> - reverse map any resource resolver mappings, ie. call ResourceResolver.map()
> - add the servlet context path at the beginning
> - (maybe check if the resource actually exists)
> (I hope this list is complete)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
