You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-dev@jackrabbit.apache.org by Angela Schreiber <an...@adobe.com> on 2012/11/27 16:12:30 UTC
Re: svn commit: r1406225 [1/2] - in /jackrabbit/oak/trunk: oak-commons/src/main/java/org/apache/jackrabbit/oak/commons/
oak-core/src/main/java/org/apache/jackrabbit/oak/security/principal/ oak-core/src/main/java/org/apache/jackrabbit/oak/security/user/...
hi michael
> rootNode.getOrAddTree("a/b/../../c/d/../../e/f", "");
>
> adds the three sub trees /a/b, /c/d and /e/f. Is this really the
> intended behaviour?
yes... see als JcrUtil in jackrabbit-commons.
kind regards
angela
Re: svn commit: r1406225 [1/2] - in /jackrabbit/oak/trunk: oak-commons/src/main/java/org/apache/jackrabbit/oak/commons/
oak-core/src/main/java/org/apache/jackrabbit/oak/security/principal/ oak-core/src/main/java/org/apache/jackrabbit/oak/security/user/...
Posted by Michael Dürig <md...@apache.org>.
On 27.11.12 15:12, Angela Schreiber wrote:
> hi michael
>
>> rootNode.getOrAddTree("a/b/../../c/d/../../e/f", "");
>>
>> adds the three sub trees /a/b, /c/d and /e/f. Is this really the
>> intended behaviour?
>
> yes... see als JcrUtil in jackrabbit-commons.
Ok, I created JCR-3465. If this is intended the Javadoc should at least
clearly state so.
However, AFAICT Node.getNode("a/b/../../c/d/../../e/f") is equal to
Node.getNode("e/f"). So I don't see why the methods in JCRUtil should
interpret path parameters any different.
Michael
>
> kind regards
> angela