[
https://issues.apache.org/jira/browse/JCRVLT-488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17251656#comment-17251656
]
Konrad Windszus edited comment on JCRVLT-488 at 12/18/20, 10:16 AM:
--------------------------------------------------------------------
According to
https://jackrabbit.apache.org/filevault/vaultfs.html#Filename_escaping
namespaces are escaped specially. The problem with a node name
{{:oak:mount-libs-nodetype}} is that {{:oak}} is incorrectly detected as
namespace prefix.
Apart from the fact that one may expect something else for the escape rule, is
there an actual problem with the escaping?
As long as the reverse unescaping does not have a problem with it I don't see a
big issue with that.
was (Author: kwin):
According to
https://jackrabbit.apache.org/filevault/vaultfs.html#Filename_escaping
namespaces are escaped specially. The problem with a node name
{{:oak:mount-libs-nodetype}} is that {{:oak}} is incorrectly detected as
namespace prefix.
Apart from the fact that one may expect something else for the escape rule, is
there an actual problem with the escaping?
> PlatformNameFormat incorrectly sets repository names for nodes with double
> colons
> ---------------------------------------------------------------------------------
>
> Key: JCRVLT-488
> URL: https://issues.apache.org/jira/browse/JCRVLT-488
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: vlt
> Affects Versions: 3.4.6
> Reporter: Robert Munteanu
> Priority: Major
>
> With a node name such as ":oak:mount-libs-nodetype" the
> {{PlatformNameFormat}} class generates a platform name of
> {{_%3aoak_mount-libs-nodetype}}, which looks incorrect :
> - leading underscore should not be there
> - second underscore should not be there, as it's not part of a namespace
> declaration
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
