This is a follow up to OAK-563. As discussed there, passing syntactically invalids paths to Oak should rather return in an IllegalArgumentException instead of a (subtype) of a RepositoryException as this is clearly a programmer's error and not an exception condition of the repository itself.
Attachments
Issue Links
relates to
OAK-658Unexpected illegal path handling on oak-jcr wrt backwards compatibility