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 2015/08/22 16:46:45 UTC
[jira] [Commented] (JCR-3902) NodeTypeDefDiff incorrectly handles
multiple residual property definitions
[ https://issues.apache.org/jira/browse/JCR-3902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14708053#comment-14708053 ]
Unico Hommes commented on JCR-3902:
-----------------------------------
Committed to trunk in revision 1697087. Committed to branch 2.10 in revision 1697088.
> NodeTypeDefDiff incorrectly handles multiple residual property definitions
> --------------------------------------------------------------------------
>
> Key: JCR-3902
> URL: https://issues.apache.org/jira/browse/JCR-3902
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Reporter: Unico Hommes
> Assignee: Unico Hommes
> Fix For: 2.10.3, 2.11.1
>
>
> The following change in node type definition should succeed:
> old.cnd:
> {code}
> [my:nodetype]
> - * (string)
> {code}
> new.cnd:
> {code}
> [my:nodetype]
> - * (string)
> - * (boolean)
> {code}
> But this fails. The reason is that property definitions are matched up using the name (in the case of residual property definitions *) as the key. In this case * (string) is matched up with * (boolean) and a change of property type is illegal, whereas it should have matched up with * (string) in which case there is no change in property type and in which case * (boolean) is a new property definition which is legal to add.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)