jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Created: (JCR-333) NodeTypeDef depends on supertype ordering
Date Mon, 06 Mar 2006 23:34:02 GMT
NodeTypeDef depends on supertype ordering
-----------------------------------------

         Key: JCR-333
         URL: http://issues.apache.org/jira/browse/JCR-333
     Project: Jackrabbit
        Type: Bug
  Components: nodetype  
    Versions: 0.9    
    Reporter: Jukka Zitting
    Priority: Minor


Currently the NodeTypeDef.setSupertypes() method simply sets the given QName array as the
supertype QName array of the defined node type, thus preserving whatever ordering a node type
parser or ultimately a node type definition file uses. This causes problems for example in
the equals() method that uses the order-sensitive Arrays.equals() method to check for equality
of the supertype QName arrays. The current implementation does therefore not consider the
node type definitions "A > B, C" and "A > C, B" as equal even though they really should
be so considered.

The same problem affects also child node and property definitions. The proper fix for this
issue would probably be to use Sets to store and handle this information.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message