[
https://issues.apache.org/jira/browse/OAK-11683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17953426#comment-17953426
]
Julian Reschke commented on OAK-11683:
--------------------------------------
[~kwin] - I see ITs failing occasionally; see
https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/org.apache.jackrabbit$oak-it/2199/testReport/org.apache.jackrabbit.oak.plugins.name/ReadWriteNamespaceRegistryTest/testInvalidNamespaceInStrictMode_SegmentTar_/
I'll back this out for now; it probably has to do with the handling of the
system property in the test.
> Prevent registration of invalid namespace URIs
> ----------------------------------------------
>
> Key: OAK-11683
> URL: https://issues.apache.org/jira/browse/OAK-11683
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: 1.82.0
>
>
> In OAK-10304 additional logging was added whenever
> {{NamespaceRegistry.registerNamespace(...)}} was called with an invalid URI.
> However registering such invalid mapping was still supported and was leading
> to subtle issues whenever the expanded name form was used as JCR method
> argument (OAK-9584).
> To prevent this violation of the JCR spec (i.e. only supporting using
> qualified node names for illegal namespace URIs) I would opt for explicitly
> throwing an exception whenever an invalid URI is registered as namespace.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
