[
https://issues.apache.org/jira/browse/OAK-9621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17442701#comment-17442701
]
Julian Reschke commented on OAK-9621:
-------------------------------------
FWIW, this (disallowing mandatory on residual definitions) might be a change in
JCR 2.0; it doesn't seem to be present in
https://www.adobe.io/experience-manager/reference-materials/spec/jcr/1.0/index.html
> Mandatory child nodes without name constraints 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. 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)
