[
https://issues.apache.org/jira/browse/SLING-7926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17324926#comment-17324926
]
Konrad Windszus edited comment on SLING-7926 at 4/19/21, 10:16 AM:
-------------------------------------------------------------------
As mentioned by [~sseifert] I don't see how this could be implemented without
breaking backwards-compatibility. There may be bundles out there which rely on
underscores which currently don't need to be escaped.
was (Author: kwin):
As mentioned by [~sseifert] I don't see how this could be implemented without
breaking backwards-compatibility. There may be bundle out there which rely on
underscored which currently don't need to be escaped.
> JSON Content Parser should support FileVault filename escaping
> --------------------------------------------------------------
>
> 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 ContentLoader 2.4.2
>
>
> 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 than the
> current recommendation of a url mangled colon of {{%3A}}.
> The exact FileVault filename escape rules are outlined at
> https://jackrabbit.apache.org/filevault/vaultfs.html#Filename_escaping.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
