jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Reschke (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OAK-7886) Re-registering node type may corrupt registry
Date Tue, 25 Jun 2019 07:29:00 GMT

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

Julian Reschke updated OAK-7886:
--------------------------------
    Fix Version/s: 1.8.14

> 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, candidate_oak_1_6,
candidate_oak_1_8
>             Fix For: 1.10.0, 1.9.11, 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)

Mime
View raw message