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 2012/09/13 00:01:08 UTC

[jira] [Commented] (SLING-2560) Support regular expressions for ResourceResolver.map configuration

    [ https://issues.apache.org/jira/browse/SLING-2560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13454414#comment-13454414 ] 

Felix Meschberger commented on SLING-2560:
------------------------------------------

The simples approach is to allow the sling:match property to actually be a replacement pattern (e.g. http://$1/$2 ) and the sling:internalRedirect property to be a regular expression (e.g. /content/([^/]+)/routed/(.*))
                
> Support regular expressions for ResourceResolver.map configuration
> ------------------------------------------------------------------
>
>                 Key: SLING-2560
>                 URL: https://issues.apache.org/jira/browse/SLING-2560
>             Project: Sling
>          Issue Type: New Feature
>          Components: JCR
>    Affects Versions: JCR Resource 2.1.0
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>
> Currently configuration in /etc/map supports using regular expressions to resolve URLs to resource paths. Such regular expression can also include replacement patterns such as
>     http/host.90/(.*)   =>  /content/host/$1
> Such replacement patterns are not easily revertible and thus such entries only influence URL resolution through ResourceResolver.resolve but not resource path mapping through ResourceResolver.map.
> As a new feature, support should be created to be able to have regular expressions with replacements patterns for path mapping such as:
>     /content/([^/]+)/routed/(.*)  => http://$1/$2
> This requires the ability to register internal paths in addition to URL paths in the /etc/map structure which map to URLs.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira