[jira] [Comment Edited] (OAK-9621) Mandatory child nodes without name constraints are not enforced

["Konrad Windszus (Jira)" <ji...@apache.org>]

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

Konrad Windszus edited comment on OAK-9621 at 11/11/21, 2:48 PM:
-----------------------------------------------------------------

Haven't tested in JR2 but according to JCR 2.0 this is a violation of the spec (and should potentially be covered in the TCK)

Update: not so sure anymore after I read https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/3_Repository_Model.html#3.7.2.4%20Mandatory

{quote}3.7.2.4.3 Mandatory and Residual Definitions
In repositories that support residual definitions, an item cannot be both mandatory and residual (see §3.7.2.1.2 Item Definition Name and Residual Definitions).{quote}


was (Author: kwin):
Haven't tested in JR2 but according to JCR 2.0 this is a violation of the spec (and should potentially be covered in the TCK)

> 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)