Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-9621

Mandatory residual (without name constraints) child nodes are not enforced

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 1.42.0
    • None
    • None
    • None

    Description

      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.

      Attachments

        Issue Links

        is related to

        Bug - A problem which impairs or prevents the functions of the product. JCRVLT-549 node cannot be deleted if it's a residual mandatory child node

        • Major - Major loss of function.
        • Resolved
        relates to

        Task - A task that needs to be done. JCR-4740 add test coverage for mandatory residual child nodes

        • Minor - Minor loss of function, or other problem where easy workaround is present.
        • Closed

        Task - A task that needs to be done. JCR-4741 add test coverage for mandatory non-residual child nodes

        • Minor - Minor loss of function, or other problem where easy workaround is present.
        • Closed
        links to

        Web Link GitHub Pull Request #414

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            kwin Konrad Windszus
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:

              Slack

                Issue deployment