[OAK-10596] Improve the test coverage of o.a.j.o.namepath.JcrPathParser

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.64.0, 1.22.21
• Component/s: core-spi
• Assignee: Manfred Baedke
• Reporter: Manfred Baedke
• Created: 10/Jan/24 14:20
• Updated: 20/Jun/24 16:59
• Resolved: 08/Apr/24 08:41

Description

JcrPathParser is mistreating some edge cases. We have to cover those with unit tests.

Issue Links

• is related to: OAK-10619 Unmapped namespace URIs should be allowed in expanded names
• is related to: OAK-10625 o.a.j.o.namepath.JcrPathParser fails with a bogus error message in the case of an unexpected EOF.
• is related to: OAK-5260 Incorrect handling of subpaths with leading left curly bracket
• is related to: OAK-10611 o.a.j.o.namepath.JcrPathParser does not handle invalid characters correctly
• is related to: OAK-10621 o.a.j.o.namepath.JcrPathParser does not accept indexed expanded names
• is related to: OAK-10624 o.a.j.o.namepath.JcrPathParser does not accept some valid local names containing '{' or '}'
• is related to: OAK-5316 Rewrite JcrPathParser and JcrNameParser with good test coverage
• is related to: OAK-5367 Strange path parsing
• is related to: OAK-10616 Make error messages from o.a.j.o.namepath.JcrNameParser/JcrPathParser consistent and less misleading