You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Tobias Bocanegra (JIRA)" <ji...@apache.org> on 2016/12/07 01:58:58 UTC

[jira] [Created] (OAK-5229) Using Node.setPrimaryType() should fail if non-matching childnodes

Tobias Bocanegra created OAK-5229:
-------------------------------------

             Summary: Using Node.setPrimaryType() should fail if non-matching childnodes
                 Key: OAK-5229
                 URL: https://issues.apache.org/jira/browse/OAK-5229
             Project: Jackrabbit Oak
          Issue Type: Bug
          Components: core
    Affects Versions: 1.5.14
            Reporter: Tobias Bocanegra


1. Assume the following:
{noformat}
/testNode [nt:unstructured]
  /unstructured_child [nt:unstructured]
{noformat}

2. setting "/testNode".setPrimaryType("nt:folder")

the above works, leaving the repository in an inconsistent state.
subsequent calls to "/testNiode/unstructured_child".setProperty() will fail:

{noformat}
javax.jcr.nodetype.ConstraintViolationException: OakConstraint0001: /test_node[[nt:folder]]: No matching definition found for child node unstructured_child with effective type [nt:unstructured]
{noformat}





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)