jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tobias Bocanegra (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-1471) Error when registering nodetype with same propdef as supertype
Date Fri, 14 Mar 2008 01:49:25 GMT

    [ https://issues.apache.org/jira/browse/JCR-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578567#action_12578567
] 

Tobias Bocanegra commented on JCR-1471:
---------------------------------------

so you're saying, if 2 defs have the same name and 'flags' they are ambiguous?
that sounds wrong to me :-) but it's probably an implementation issue.

i'll revert the changes but update the error message a bit,



> Error when registering nodetype with same propdef as supertype
> --------------------------------------------------------------
>
>                 Key: JCR-1471
>                 URL: https://issues.apache.org/jira/browse/JCR-1471
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: nodetype
>    Affects Versions: 1.4, core 1.4.1
>            Reporter: Tobias Bocanegra
>            Assignee: Tobias Bocanegra
>             Fix For: 1.5
>
>
> error in check:
>                                 if (pd.getRequiredType() == epd.getRequiredType()
>                                         && pd.isMultiple() == epd.isMultiple())
{
>                                     // conflict
>                                     String msg = "The property definition for '"
>                                             + name + "' in node type '"
>                                             + def.getDeclaringNodeType()
>                                             + "' conflicts with node type '"
>                                             + existingDef.getDeclaringNodeType()
>                                             + "': ambiguous property definition";
>                                     log.debug(msg);
>                                     throw new NodeTypeConflictException(msg);
>                                 }
> if needs to be inverted.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message