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

Miroslav Smiljanic edited comment on OAK-9621 at 11/12/21, 12:11 PM:
---------------------------------------------------------------------

+1 for documenting the deviation from the spec. 

I think we should keep the current behaviour. In addition expose configuration 
option (not enabled by default) that will mandate behaviour as per spec.

Migration to the structure required by the spec can be implemented as oak-run 
command. 


was (Author: smiroslav):
+1 for documenting the deviation form the spec. 

I think we should keep the current behaviour. In addition expose configuration 
option (not enabled by default) that will mandate behaviour as per spec.

Migration to the structure required by the spec can be implemented as oak-run 
command. 

> Mandatory residual (without name constraints) child nodes are not enforced
> --------------------------------------------------------------------------
>
>                 Key: OAK-9621
>                 URL: https://issues.apache.org/jira/browse/OAK-9621
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>    Affects Versions: 1.42.0
>            Reporter: Konrad Windszus
>            Priority: Major
>
> Node types may have mandatory child nodes.
> Those constraints are not enforced when creating new nodes or deleting the 
> mandatory child node if the mandatory child node has no name constraint (i.e. 
> is residual). It works well if the mandatory child node has a name constraint 
> as well.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to