[
https://issues.apache.org/jira/browse/SLING-7926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16891974#comment-16891974
]
Jason E Bailey commented on SLING-7926:
---------------------------------------
You're correct, I was looking at both of them at that time and switched names.
I'll Update
> JSON Content Loading should support namespace mangling
> ------------------------------------------------------
>
> Key: SLING-7926
> URL: https://issues.apache.org/jira/browse/SLING-7926
> Project: Sling
> Issue Type: Improvement
> Reporter: Jason E Bailey
> Assignee: Jason E Bailey
> Priority: Major
> Fix For: JCR Content Parser 1.2.8
>
>
> Currently it's possible to define a json file with a name that matches a
> mangled namespace. Which then makes the file unable to be accessed from the
> ResourceResolver
> i.e. importing a file `_jcr_content.json` will create the node `_jcr_content`
> which cannot then be resolved as the resource resolver will attempt to
> convert `_jcr_content` to `jcr:content` supporting namespace mangling will
> additionally provide a cleaner `colon` support then the current
> recommendation of a url mangled colon of `%3A`
>
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
