You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2018/11/08 15:44:00 UTC

[jira] [Resolved] (OAK-7886) Re-registering node type may corrupt registry

     [ https://issues.apache.org/jira/browse/OAK-7886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcel Reutegger resolved OAK-7886.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.9.11

Fixed in trunk: http://svn.apache.org/r1846162

> Re-registering node type may corrupt registry
> ---------------------------------------------
>
>                 Key: OAK-7886
>                 URL: https://issues.apache.org/jira/browse/OAK-7886
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.8.0
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>            Priority: Major
>             Fix For: 1.10, 1.9.11
>
>         Attachments: OAK-7886.patch
>
>
> Re-registering an existing node type may corrupt the registry. This happens for node types that are not mixins and do not extend from other primary types (except for the implicit {{nt:base}}). After re-registering such a node type the {{jcr:supertypes}} list does not have the {{nt:base}} anymore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)