[
https://issues.apache.org/jira/browse/SLING-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved SLING-1726.
--------------------------------------
Resolution: Fixed
Fixed in Rev. 992220.
> Namespace mangling is broken for path segments with a leading underscore
> ------------------------------------------------------------------------
>
> Key: SLING-1726
> URL: https://issues.apache.org/jira/browse/SLING-1726
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: JCR Resource 2.0.8
>
>
> Consider a node at
> /content/_test/jcr:content
> With namespace mangling, this node should be accessible with the URL path
> /content/_test/_jcr_content
> where the "_jcr_" prefix is converted to the correct namespace prefix "jcr:"
> but the prefixed underscore "_" of the "_test" node must be left unmodified.
> The regular expression to find and replace the namespace prefixes --
> "/_([^_]+)_" -- is setup to match anything enclosed with "/_" and "_". Thus
> the test path would match "/_test/_" and fail to convert this (of course
> test/ is not a valid, registered namespace prefix). But subsequently the real
> prefix -- "_jcr_" -- is actually missed.
> The regular expression must be modified to not match any slash characters,
> thus "/_([^_/]+)_"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
