[
https://issues.apache.org/jira/browse/OAK-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13496189#comment-13496189
]
Michael Dürig commented on OAK-426:
-----------------------------------
We discussed on several occasions that path handling should be done in oak-jcr
(see for example http://markmail.org/message/fplu4dn47g23yoav) and we design
the oak-core API accordingly. The relative path parameter in
{{TreeLocation.getChild()}} was introduced as a concession and it was possible
to do so since this does not affect other areas. However assigning special
meanings to certain names starts to blur the separation of concerns namely
interpretation of paths encoded into strings and navigation of trees. This
would also affect all other parts of the oak-api where names are affected since
these would have to be checked for special names as well.
> OAK-API: Deal with names and relativePaths consisting/containing "." and ".."
> -----------------------------------------------------------------------------
>
> Key: OAK-426
> URL: https://issues.apache.org/jira/browse/OAK-426
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: core
> Reporter: angela
>
> i just run into another place where i would need to work around
> missing support for the current (".") and parent ("..") element
> in the TreeLocation.
> IMO it would make sense to add this to TreeLocation#getChild... maybe
> even rename it to TreeLocation#getLocation(String relativePath)?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
