[OAK-1174] Inconsistent handling of invalid names/paths

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 0.20
• Component/s: jcr
• Assignee: Jukka Zitting
• Reporter: Michael Dürig
• Created: 13/Nov/13 08:49
• Updated: 17/Sep/15 04:34
• Resolved: 28/Mar/14 16:31

Description

Passing an invalid name to a JCR method might or might not throw a RepositoryException depending on whether name re-mappings exist or not:

session.itemExists("/jcr:cont]ent");

returns false if no name re-mappings exist but throws a RepositoryException otherwise.

Issue Links

• is related to: OAK-1891 Regression: non-space whitespace not allowed in item names
• is related to: OAK-1624 Item names with trailing spaces should not be allowed
• is related to: OAK-3412 Node name having non space whitspace chars should not be allowed
• is related to: OAK-1179 Use dedicated Path class for handling paths in Oak
• relates to: OAK-1168 Invalid JCR paths not caught
• relates to: OAK-3395 RevisionGC fails for JCR paths having line feed characters