[OAK-999] Version creates frozenNode children with orignial NoteType instead of frozenNode

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.8
• Fix Version/s: 0.9
• Component/s: jcr
• Assignee: Marcel Reutegger
• Reporter: Christan Keller
• Created: 04/Sep/13 17:39
• Updated: 20/Sep/13 07:01
• Resolved: 11/Sep/13 06:32

Description

For a Version the the children of a the Versions FrozenNode have the the NodeType of their origin if they are not rferenceable. Expected is nt:frozenNode.

The JCR Spec is not explicit on the node-type for this Nodes but it is not Compatible with JR2

Dummy Test Case that just starts a Oak Repository

public class Issue extends RepositoryBaseTest {

    @Test
    public void testVersionChild() throws RepositoryException {
        Session admin = getAdminSession();
        Node parent = admin.getRootNode().addNode(getClass().getSimpleName()+System.currentTimeMillis(), JcrConstants.NT_UNSTRUCTURED);
        Node child = parent.addNode("child");
        parent.addMixin(JcrConstants.MIX_VERSIONABLE);
        admin.save();
        VersionManager vm = admin.getWorkspace().getVersionManager();
        Version v = vm.checkin(parent.getPath());

        Node frozenChild = v.getFrozenNode().getNode(child.getName());
        Assert.assertEquals(JcrConstants.NT_FROZENNODE, frozenChild.getPrimaryNodeType().getName());
    }

}