[OAK-5367] Strange path parsing

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: core
• Assignee: Thomas Mueller
• Reporter: Thomas Mueller
• Created: 22/Dec/16 11:41
• Updated: 11/Jan/24 13:59

Description

Incorrect handling of path with "{" was fixed in OAK-5260, but the behavior of the JcrPathParser is still strange. For example:

• the root node, "/", is mapped to "/", and the current node, "." is mapped to "". But "/." is mapped to the current node (should be root node).
• "/parent/./childA2" is mapped to "/parent/childA2" (which is fine), but "/parent/.}/childA2" is also mapped to "/parent/childA2".
• "}{" and "}[" and "}}[" are mapped to the current node. So are ".[" and "/[" and ".}". And "}{test" is mapped to "}{test", which is inconsistent-weird.
• "x[1]}" is mapped to "x".

All that weirdness should be resolved. Some seem to be just weird, but some look like they could become a problem at some point ("}{").

Issue Links

• relates to: OAK-5260 Incorrect handling of subpaths with leading left curly bracket
• relates to: OAK-10596 Improve the test coverage of o.a.j.o.namepath.JcrPathParser