[
https://issues.apache.org/jira/browse/OAK-10523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17781402#comment-17781402
]
Konrad Windszus edited comment on OAK-10523 at 10/31/23 2:44 PM:
-----------------------------------------------------------------
Instead of modifying the behaviour of Node.getName() one could also fix/relax
the handling of APIs called on top of Node.getName(). IIUC then this was faced
with
[{{NameResolver.getQName(String)}}|https://jackrabbit.apache.org/api/trunk/org/apache/jackrabbit/spi/commons/conversion/NameResolver.html#getQName-java.lang.String-]
although the javadoc currently explicitly states that it throws
{{IllegalNameException}} when an invalid JCR name is passed.
was (Author: kwin):
Instead of modifying the behaviour of Node.getName() one could also fix/relax
the handling of APIs called on top of Node.getName(). IIUC then this was faced
with
[{{NameResolver.getQName(String)}}|https://jackrabbit.apache.org/api/trunk/org/apache/jackrabbit/spi/commons/conversion/NameResolver.html#getQName-java.lang.String-]
> Basic SNS support returns invalid node names
> --------------------------------------------
>
> Key: OAK-10523
> URL: https://issues.apache.org/jira/browse/OAK-10523
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
> Reporter: Julian Reschke
> Priority: Minor
>
> When encountering names using index notation in storage, oak-jcr treats the
> index suffix as part of the name. This causes issues with other components
> that assume that the result of {{Node.getName()}} is indeed a valid JCR name.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
