[OAK-1179] Use dedicated Path class for handling paths in Oak

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Component/s: core, jcr
• Assignee: Jukka Zitting
• Reporter: Michael Dürig
• Created: 13/Nov/13 16:09
• Updated: 16/Feb/15 15:09
• Resolved: 16/Feb/15 15:09

Description

As discussed (for example here several times before using naked strings for paths is troublesome. OAK-1168 and OAK-1174 are only the latest of a long history of issues we suffered because of this.

While wrapping the path and related entities into dedicated classes will add some overhead at first. It will OTOH clearly communicate the intend of what otherwise are just naked strings. In addition it will introduce a clear boundary for optimisations while in the string case these blur with the client code.

I thus propose to introduce a dedicated class for paths in Oak. Such a class could serve as a container for the string, which is the lazily acted upon as required.

Issue Links

• relates to: OAK-1216 Path parsing must support SNS indexes, irrespective of SNS support
• relates to: OAK-204 short cutting the name mapping breaks path validation in value factory
• relates to: OAK-1168 Invalid JCR paths not caught
• relates to: OAK-1174 Inconsistent handling of invalid names/paths
• relates to: OAK-74 avoid use of "internal" namespace