Uploaded image for project: 'Jackrabbit Content Repository'
  1. Jackrabbit Content Repository
  2. JCR-3902

NodeTypeDefDiff incorrectly handles multiple residual property definitions

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

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 2.10.2, 2.11.1
    • None
    • None

    Description

      The following change in node type definition should succeed:
      old.cnd:

      [my:nodetype]
      - * (string)
      

      new.cnd:

      [my:nodetype]
      - * (string)
      - * (boolean)
      

      But this fails. The reason is that property definitions are matched up using the name (in the case of residual property definitions *) as the key. In this case * (string) is matched up with * (boolean) and a change of property type is illegal, whereas it should have matched up with * (string) in which case there is no change in property type and in which case * (boolean) is a new property definition which is legal to add.

      Attachments

        Issue Links

        Activity

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

          People

            unico@apache.org Unico Hommes
            unico@apache.org Unico Hommes
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment