Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <475138535.1250035094794.JavaMail.jira@brutus>
Date: Tue, 11 Aug 2009 16:58:14 -0700 (PDT)
From: "Lars Michele (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Created: (JCR-2257) Removal of a node with shared subnodes
 fails
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Removal of a node with shared subnodes fails
--------------------------------------------

                 Key: JCR-2257
                 URL: https://issues.apache.org/jira/browse/JCR-2257
             Project: Jackrabbit Content Repository
          Issue Type: Bug
          Components: jackrabbit-core
    Affects Versions: 2.0-alpha7
            Reporter: Lars Michele


A simple testcase:

Set up (first transaction):
Node a1 = testRootNode.addNode("a1");
Node a2 = testRootNode.addNode("a2");
a2.addMixin("mix:shareable");
session.save();
// now we have a shareable node N with path a2

Workspace workspace = session.getWorkspace();
String path = a1.getPath() + "/b1";
workspace.clone(workspace.getName(), a2.getPath(), path, false);
session.save();
// now we have another shareable node N' in the same shared set as N with path a1/b1

Test(second transaction):
testRootNode.remove("a1");
session.save();

At least in a transactional repository the node will not be removed, an error will be thrown instead.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.