[ https://issues.apache.org/jira/browse/OAK-10616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17809935#comment-17809935 ]
Manfred Baedke edited comment on OAK-10616 at 2/16/24 9:41 AM: --------------------------------------------------------------- trunk (1.62.0): [4d29e3f7|https://github.com/apache/jackrabbit-oak/commit/4d29e3f7838458f4a5627d93bc0f7831ff8bd6bf] was (Author: baedke): trunk: [4d29e3f7|https://github.com/apache/jackrabbit-oak/commit/4d29e3f7838458f4a5627d93bc0f7831ff8bd6bf] > Make error messages from o.a.j.o.namepath.JcrNameParser/JcrPathParser > consistent and less misleading > ----------------------------------------------------------------------------------------------------- > > Key: OAK-10616 > URL: https://issues.apache.org/jira/browse/OAK-10616 > Project: Jackrabbit Oak > Issue Type: Task > Components: core-spi > Reporter: Manfred Baedke > Assignee: Manfred Baedke > Priority: Minor > Fix For: 1.62.0 > > > JcrPathParser delegates name parsing to JcrNameParser, which may lead to > error messages not including the path (contrary to all other error messages > from the JcrPathParser). > JcrPathParser fails with a bogus error message in the case of an unexpected > EOF (trying to insert EOF into the human readable error message). > Also in the case of an empty local name in a prefixed JCR name, the error > message depends on the following characters and is misleading. -- This message was sent by Atlassian Jira (v8.20.10#820010)