[ 
https://issues.apache.org/jira/browse/OAK-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13759027#comment-13759027
 ] 

angela commented on OAK-999:
----------------------------

maybe the definition of the nt:frozenNode is simply wrong by defining the 
jcr:frozenUuid property as mandatory? in jackrabbit-core nobody would have 
noticed since the all nodes had a uuid anyway...
                
> Version creates frozenNode children with orignial NoteType instead of 
> frozenNode
> --------------------------------------------------------------------------------
>
>                 Key: OAK-999
>                 URL: https://issues.apache.org/jira/browse/OAK-999
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: jcr
>    Affects Versions: 0.8
>            Reporter: Christan Keller
>
> 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
> {code}
> 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());
>     }
> }
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to