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

Michael Dürig commented on OAK-1013:
------------------------------------

[~chkeller] is this still an issue that is blocking you? Otherwise I think we 
should resolve it as wont fix. 

> 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
>            Priority: Minor
>         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)

Reply via email to