You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2008/12/14 23:23:44 UTC
[jira] Closed: (SLING-773) ResourceResolver.map should handle paths
with selectors and extensions
[ https://issues.apache.org/jira/browse/SLING-773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger closed SLING-773.
-----------------------------------
Resolution: Fixed
Added more unit tests in Rev. 726559.
Closing this issue now.
> ResourceResolver.map should handle paths with selectors and extensions
> ----------------------------------------------------------------------
>
> Key: SLING-773
> URL: https://issues.apache.org/jira/browse/SLING-773
> Project: Sling
> Issue Type: Improvement
> Components: API, JCR Resource
> Affects Versions: JCR Resource 2.0.4, API 2.0.4
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: JCR Resource 2.0.4, API 2.0.4
>
>
> Currently the ResourceResolver.map methods are specified to take resource path strings. In real life the path at hand to be mapped may also be a resource path plus any selectors and extension prepared for being a link in an HTML page. In these cases, it would be valuable if the map methods could in fact first cut off the selectors and extension before finding the resource to apply and sling:alias mappings.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.