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

Malformed node type definition when reregistered after upgrade

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

Details

    • Bug
    • Status: Closed
    • Blocker
    • Resolution: Fixed
    • 1.3.10
    • 1.2.16, 1.4, 1.4.0
    • core, jcr
    • None

    Description

      When a node type is reregistered after an upgrade from an earlier release, the resulting node type definition may be malformed. As noted in OAK-3584, the node type representation in content was not compliant with JCR already before. As explained here the situation after an upgrade is even worse: http://markmail.org/message/7kjkqlt3erbocpin

      Attachments

        Issue Links

        Activity

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

          People

            mreutegg Marcel Reutegger
            mreutegg Marcel Reutegger
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment