jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] [Reopened] (OAK-1013) Node.addNode(name) different behavior from JR if NodeType resolves to an abstract
Date Wed, 05 Mar 2014 08:42:43 GMT

     [ https://issues.apache.org/jira/browse/OAK-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael Dürig reopened OAK-1013:
--------------------------------


Reopening since [~marett] brought up some concerns. Could you please recap these here on the
issue?

> Node.addNode(name) different behavior from JR if NodeType resolves to an abstract
> ---------------------------------------------------------------------------------
>
>                 Key: OAK-1013
>                 URL: https://issues.apache.org/jira/browse/OAK-1013
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: jcr
>    Affects Versions: 0.8
>            Reporter: Christan Keller
>            Assignee: Michael Dürig
>            Priority: Minor
>             Fix For: 0.18
>
>         Attachments: Issue.java
>
>
> In Jackrabbit, if you used node.addNode(name) and the NodeType resolved to an abstract
like nt:base Jackrabbit still persisted the new Node.
> In Oak a ConstraintViolationException is thrown.
> While the Oak behavior is fully Spec complient, it still may be a migration issue for
JR users.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message