Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
1.5.15
-
None
-
None
Description
As discussed in OAK-5260 the implementation of the JcrPathParser and possibly also the JcrNameParser are not ideal, i.e. there are potentially many bugs hiding in edge-case scenarios. The parsers' test coverage is also lacking, which is problematic as these code paths get executed very frequently.