You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Jason E Bailey (JIRA)" <ji...@apache.org> on 2018/10/08 18:34:00 UTC

[jira] [Assigned] (SLING-7926) JSON Content Loading should support namespace mangling

     [ https://issues.apache.org/jira/browse/SLING-7926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason E Bailey reassigned SLING-7926:
-------------------------------------

    Assignee: Jason E Bailey

> 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.3#76005)