[OAK-732] Change TreeLocation.getChild() to only accept direct child nodes (not relative paths)

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.7
• Component/s: core
• Assignee: Michael Dürig
• Reporter: Michael Dürig
• Created: 02/Apr/13 10:34
• Updated: 21/May/13 11:18
• Resolved: 03/Apr/13 13:26

Description

As mentioned on the list [1] resolving relative paths in TreeLocation.getChild() is expensive. Since not all clients need this functionality but all inherit the additional performance penalty, I suggest to remove support for relative paths and move that functionality into a helper class (e.g. LocationHelper).

     /**
-     * Navigate to a child through a relative path. A relative path consists of a
-     * possibly empty lists of names separated by forward slashes.
-     * @param relPath  relative path to the child
+     * Navigate to a child of the given {@code name}.
+     * @param name  name of the child
      * @return  a {@code TreeLocation} for a child with the given {@code name}.
      */
     @Nonnull
-    TreeLocation getChild(String relPath);
+    TreeLocation getChild(String name);

[1] http://markmail.org/message/o72qikdvyr5xyxfu

Issue Links

• is related to: OAK-426 OAK-API: Deal with names and relativePaths consisting/containing "." and ".."