[dna-issues] [JBoss JIRA] Updated: (DNA-349) AbstractJcrNode.addNode Does Not Add jcr:uuid Property if Primary Type Extends mix:referenceable
Brian Carothers (JIRA)
jira-events at lists.jboss.org
Fri Apr 10 20:29:33 EDT 2009
[ https://jira.jboss.org/jira/browse/DNA-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Carothers updated DNA-349:
--------------------------------
Attachment: DNA-349.patch
Here's a patch that corrects the issue. I've tested it locally with an extra type registered with the uncommitted type registration code.
> AbstractJcrNode.addNode Does Not Add jcr:uuid Property if Primary Type Extends mix:referenceable
> ------------------------------------------------------------------------------------------------
>
> Key: DNA-349
> URL: https://jira.jboss.org/jira/browse/DNA-349
> Project: DNA
> Issue Type: Bug
> Components: JCR
> Affects Versions: 0.3
> Reporter: Brian Carothers
> Priority: Minor
> Attachments: DNA-349.patch
>
>
> If a node is loaded from the repository with a primary type that has mix:referenceable as a supertype, the mandatory, protected jcr:uuid property is properly set. If a new node is added with the same primary type, the jcr:uuid property is not set.
> When the TCK tests are changed to use a default node type which has mix:referenceable as a supertype (which must be done to make the tests in SetValueNodeTest pass), this issue causes NodeAddMixinTest.testAddMixinReferenceable to fail.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the dna-issues
mailing list