[OAK-230] Review and fix inconsistent usage of oak-path in oak-jcr

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.5
• Assignee: Michael Dürig
• Reporter: Angela Schreiber
• Created: 03/Aug/12 08:20
• Updated: 01/Oct/12 11:40
• Resolved: 20/Aug/12 13:39

Description

as stated in the main issues there seems to be some inconsistency when it
comes to passing a path to the oak api in oak-jcr. this should be
reviewed and fixed throughout the project and the javadoc and method signature
of the affected methods (in particular in *Delegate) should be adjusted
such that it's unambiguous with path parameter are expected to be passed
to the method calls which paths are being returned.

for example:

• SessionDelegate#getNode
• SessionDelegate#getNodeByIdentifier