[
https://issues.apache.org/jira/browse/JCR-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506331#comment-13506331
]
Michael Dürig commented on JCR-3465:
------------------------------------
+0 for changing this s.t. "a/b/../../c/d../../e/f" has the same effect as "a/b"
(this is what Felix means with fixing I guess). However if backward
compatibility turns out to be the bigger concern here, we should be more
explicit about this case in the Javadoc.
> JcrUtils.getOrCreateByPath() creates a whole subtree instead of a single
> branch
> -------------------------------------------------------------------------------
>
> Key: JCR-3465
> URL: https://issues.apache.org/jira/browse/JCR-3465
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Reporter: Michael Dürig
> Priority: Minor
>
> Given a leaf node n,
> JcrUtils.getOrCreateByPath(n, "a/b/../../c/d/../../e/f", false, null, null,
> true);
> will result in paths a/b, c/d and e/f being added to n where I'd only expect
> the path e/f.
--
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
