[
https://issues.apache.org/jira/browse/SLING-12439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated SLING-12439:
-----------------------------------
Description:
In JCR, a namespace name is defined to be an absolute URI (see
<https://developer.adobe.com/experience-manager/reference-materials/spec/jcr/2.0/3_Repository_Model.html#3.2%20Names>)
Repoinit, however, seems to allow "simple" names such as "foo".
These names break in the JCR API, because it will assume that "\{foo\}bar" will
parse as "local" name, not an expanded name (in the namespace "foo").
Optimally, these would be rejected, but I assume that'll break compatibilty.
Maybe the documentation could be improved and/or a warning be generated?
was:
In JCR, a namespace name is defined to be an absolute URI (see
<https://developer.adobe.com/experience-manager/reference-materials/spec/jcr/2.0/3_Repository_Model.html#3.2%20Names>)
Repoinit, however, seems to allow "simple" names such as "foo".
These names break in the JCR API, because it will assume that "{foo}bar" will
parse as "local" name, not an expanded name (in the namespace "foo").
Optimally, these would be rejected, but I assume that'll break compatibilty.
Maybe the documentation could be improved and/or a warning be generated?
> repoinit allows invalid namespace names (URIs)
> ----------------------------------------------
>
> Key: SLING-12439
> URL: https://issues.apache.org/jira/browse/SLING-12439
> Project: Sling
> Issue Type: Bug
> Components: Repoinit
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Minor
>
> In JCR, a namespace name is defined to be an absolute URI (see
> <https://developer.adobe.com/experience-manager/reference-materials/spec/jcr/2.0/3_Repository_Model.html#3.2%20Names>)
> Repoinit, however, seems to allow "simple" names such as "foo".
> These names break in the JCR API, because it will assume that "\{foo\}bar"
> will parse as "local" name, not an expanded name (in the namespace "foo").
> Optimally, these would be rejected, but I assume that'll break compatibilty.
> Maybe the documentation could be improved and/or a warning be generated?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
