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

Posted to dev@jackrabbit.apache.org by "Unico Hommes (JIRA)" <ji...@apache.org> on 2014/12/10 14:50:12 UTC

[jira] [Resolved] (JCR-3840) NodeTypeDefDiff does not take same-name child type definitions into account

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

Unico Hommes resolved JCR-3840.
-------------------------------
    Resolution: Fixed

> NodeTypeDefDiff does not take same-name child type definitions into account
> ---------------------------------------------------------------------------
>
>                 Key: JCR-3840
>                 URL: https://issues.apache.org/jira/browse/JCR-3840
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>            Reporter: Unico Hommes
>            Assignee: Unico Hommes
>             Fix For: 2.6.6, 2.8.1, 2.9.1
>
>
> The following is a legal cnd, accepted both by jackrabbit, and not prohibited by the JCR spec:
> [type]
> + child (type1)
> + child (type2)
> This scenario is not taken into account by NodeTypeDefDiff, which leads to node types wrongly failing to reload or wrongly succeeding to reload, depending on the situation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)