You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2021/09/17 09:06:00 UTC
[jira] [Created] (SLING-10821) Support resource types with
characters invalid in zip entry names
Konrad Windszus created SLING-10821:
---------------------------------------
Summary: Support resource types with characters invalid in zip entry names
Key: SLING-10821
URL: https://issues.apache.org/jira/browse/SLING-10821
Project: Sling
Issue Type: Bug
Components: Maven Plugins and Archetypes
Affects Versions: Scripting Bundle Maven Plugin 0.4.0
Reporter: Konrad Windszus
Fix For: Scripting Bundle Maven Plugin 0.5.0
Sling does not limit the character set to use for a resource type. For example a colon is perfectly valid (also in JCR names). As the resource type is directly determined from the zip entry name but the filesystem imposes several limitations (https://en.wikipedia.org/wiki/Filename#Comparison_of_filename_limitations) some kind of escaping need to be supported to allow giving arbitrary resource types just via path name. Filevault Content Packages for example leverage these escaping rules: http://jackrabbit.apache.org/filevault/vaultfs.html#Filename_escaping.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)