[jira] [Commented] (SLING-7926) JSON Content Loading should support namespace mangling
[ https://issues.apache.org/jira/browse/SLING-7926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Commented] (SLING-7926) JSON Content Loading should support namespace mangling
[ https://issues.apache.org/jira/browse/SLING-7926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16891876#comment-16891876 ] Radu Cotescu commented on SLING-7926: - [~jebailey], isn't this issue about the JCR Content Loader? > 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)
[jira] [Commented] (SLING-7926) JSON Content Loading should support namespace mangling
[ https://issues.apache.org/jira/browse/SLING-7926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16614913#comment-16614913 ] Jason E Bailey commented on SLING-7926: --- [~sseif...@pro-vision.de] I'm not suggesting eliminating the URL escaping, rather to add the ability to handle the underlined formatting. # I'd like to at least try to be consistent with how names are handled # As I mentioned being able to import data in such a way as to make it inaccessible is an issue. If it's an addition there shouldn't be a problem with backward compatibility. > 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 >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)
[jira] [Commented] (SLING-7926) JSON Content Loading should support namespace mangling
[
https://issues.apache.org/jira/browse/SLING-7926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16614877#comment-16614877
]
Stefan Seifert commented on SLING-7926:
---
have a look at
https://sling.apache.org/documentation/bundles/content-loading-jcr-contentloader.html#file-name-escaping
there is already support for node names like "jcr:content", but not with the
same escaping rules like {{_jcr_content}}, but with URI encoding e.g.
{{jcr%3Acontent}}.
this may be strange, but changing this now would break backwards compatibility
i suppose.
> 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
>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)
