[
https://issues.apache.org/jira/browse/OAK-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig resolved OAK-1013.
--------------------------------
Resolution: Won't Fix
Fix Version/s: 0.18
Assignee: Michael Dürig
Resolving as won't fix. Please reopen if this necessary.
> 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.1.5#6160)
