Description
JcrPathParser is mistreating some edge cases. We have to cover those with unit tests.
Attachments
Issue Links
- is related to
-
OAK-10619 Unmapped namesspace URIs should be allowed in expanded names
- Open
-
OAK-10625 o.a.j.o.namepath.JcrPathParser fails with a bogus error message in the case of an unexpected EOF.
- Resolved
-
OAK-5260 Incorrect handling of subpaths with leading left curly bracket
- Closed
-
OAK-10611 o.a.j.o.namepath.JcrPathParser does not handle invalid characters correctly
- Closed
-
OAK-10621 o.a.j.o.namepath.JcrPathParser does not accept indexed expanded names
- Closed
-
OAK-10624 o.a.j.o.namepath.JcrPathParser does not accept some valid local names containing '{' or '}'
- Closed
-
OAK-5316 Rewrite JcrPathParser and JcrNameParser with good test coverage
- Open
-
OAK-5367 Strange path parsing
- Open
-
OAK-10616 Make error messages from o.a.j.o.namepath.JcrNameParser/JcrPathParser consistent and less misleading
- Closed