sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason E Bailey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SLING-7926) JSON Content Loading should support namespace mangling
Date Fri, 14 Sep 2018 14:20:00 GMT

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

Jason E Bailey commented on SLING-7926:
---------------------------------------

[~sseifert@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)

Mime
View raw message