You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Thomas Mueller (JIRA)" <ji...@apache.org> on 2012/05/30 18:10:24 UTC

[jira] [Resolved] (JCR-3324) TCK: GetQueryTest.testGetQuery() unnecessarily uses a same name sibling

     [ https://issues.apache.org/jira/browse/JCR-3324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Mueller resolved JCR-3324.
---------------------------------

    Resolution: Fixed
    
> TCK: GetQueryTest.testGetQuery() unnecessarily uses a same name sibling
> -----------------------------------------------------------------------
>
>                 Key: JCR-3324
>                 URL: https://issues.apache.org/jira/browse/JCR-3324
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-jcr-tests
>            Reporter: Thomas Mueller
>            Assignee: Thomas Mueller
>
> The test case GetQueryTest.testGetQuery() first creates a node testRoot/node1:
>     testRootNode.addNode(nodeName1, testNodeType);
> and then creates another node with the same name below:
>     Node stored = q.storeAsNode(testRoot + "/" + nodeName1);
> This results in a same name sibling, which is later removed:
>     stored.remove();
> But the test case isn't about same name siblings, and could store the node under a different name instead:
>     Node stored = q.storeAsNode(testRoot + "/storedQuery");

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira