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 "Julian Reschke (JIRA)" <ji...@apache.org> on 2019/07/09 15:39:00 UTC
[jira] [Updated] (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 ]
Julian Reschke updated OAK-7886:
--------------------------------
Labels: candidate_oak_1_0 candidate_oak_1_2 candidate_oak_1_4 (was: candidate_oak_1_0 candidate_oak_1_2 candidate_oak_1_4 candidate_oak_1_6)
> 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.0, 1.2, 1.4.0, 1.6.0, 1.8.0
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Priority: Major
> Labels: candidate_oak_1_0, candidate_oak_1_2, candidate_oak_1_4
> Fix For: 1.10.0, 1.9.11, 1.6.18, 1.8.14
>
> 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)