Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Date: Thu, 24 Mar 2011 09:27:05 +0000 (UTC)
From: "Marlis Lamp (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Message-ID: 
 <165457980.8073.1300958825745.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (JCR-2930) same named child nodes disappear on
 restore
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

same named child nodes disappear on restore
-------------------------------------------

                 Key: JCR-2930
                 URL: https://issues.apache.org/jira/browse/JCR-2930
             Project: Jackrabbit Content Repository
          Issue Type: Bug
          Components: jackrabbit-core
    Affects Versions: 2.2.4
            Reporter: Marlis Lamp
            Priority: Critical


When restoring a versionable node which has several (non-versionable) child nodes with the same name, some child nodes disappear. 

            Node node = session.getRootNode().addNode("myNode");
            node.addMixin("mix:versionable");
            for (int i = 1; i < 6; i++) {
                Node child = node.addNode("child");
                child.setProperty("name", "child_"+i);
            }
            session.save();
            VersionManager versionManager = session.getWorkspace().getVersionManager();
            versionManager.checkin(node.getPath());
            System.out.println("number of child nodes: " + node.getNodes().getSize());

            versionManager.checkout(node.getPath());
            node.getNode("child").setProperty("name", "modified");
            session.save();
            Version baseVersion = versionManager.getBaseVersion(node.getPath());
            versionManager.restore(baseVersion, true);
            System.out.println("number of child nodes in restored node: "+node.getNodes().getSize());


produces the following output:

number of child nodes: 5
number of child nodes in restored node: 3

Giving unique names or adding the mixin versionable to the child nodes solves the problem.


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira