[ http://issues.apache.org/jira/browse/JCR-505?page=all ]

Marcel Reutegger resolved JCR-505.
----------------------------------

    Fix Version/s: 1.1
       Resolution: Fixed

Changed clean-up code to only remove child nodes that are not protected nor 
mandatory.

Fixed in revision: 427978

Thank you for reporting this issue.

> TCK: AbstractJCRTest fails if setUp/tearDown cannot remove children of test 
> node
> --------------------------------------------------------------------------------
>
>                 Key: JCR-505
>                 URL: http://issues.apache.org/jira/browse/JCR-505
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: test
>            Reporter: David Pitfield
>             Fix For: 1.1
>
>
> If the test node exists, the setUp and tearDown methods remove all its child 
> nodes.  In some repositories these child nodes may be mandatory or protected, 
> causing test setup/teardown to fail.
> Proposal: tolerate exceptions thrown in removing a child node in test 
> setup/teardown.
> --- ../AbstractJCRTest.java     (revision 422074)
> +++ ../AbstractJCRTest.java     (working copy)
> @@ -344,7 +344,11 @@
>                  // clean test root
>                  testRootNode = root.getNode(testPath);
>                  for (NodeIterator children = testRootNode.getNodes(); 
> children.hasNext();) {
> -                    children.nextNode().remove();
> +                    try {
> +                      children.nextNode().remove();
> +                    } catch (RepositoryException e) {
> +                      // consume
> +                    }
>                  }
>              } else {
>                  // create nodes to testPath
> @@ -375,7 +379,11 @@
>                          // clean test root
>                          testRootNode = root.getNode(testPath);
>                          for (NodeIterator children = 
> testRootNode.getNodes(); children.hasNext();) {
> -                            children.nextNode().remove();
> +                            try {
> +                              children.nextNode().remove();
> +                            } catch (RepositoryException e) {
> +                              // consume
> +                            }
>                          }
>                          root.save();
>                      }

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to