[#JCR-333] NodeTypeDef depends on supertype ordering

Jackrabbit Content Repository

NodeTypeDef depends on supertype ordering

Created: 07/Mar/06 07:33 AM Updated: 13/Oct/06 04:07 PM

Return to search

Component/s:

nodetype

Affects Version/s:

0.9

Fix Version/s:

1.0

Time Tracking:

Not Specified

Resolution Date:

09/Mar/06 01:12 AM

Description

« Hide

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.

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

Stefan Guggisberg made changes - 07/Mar/06 04:41 PM

Field	Original Value	New Value
Assignee		Stefan Guggisberg [ stefan@jira ]

Stefan Guggisberg made changes - 09/Mar/06 01:12 AM

Resolution		Fixed [ 1 ]
Status	Open [ 1 ]	Resolved [ 5 ]

Jukka Zitting made changes - 21/Mar/06 06:20 AM

Affects Version/s		1.0 [ 12310154 ]
Fix Version/s		1.1 [ 12310346 ]

Jukka Zitting made changes - 29/Mar/06 02:50 AM

Affects Version/s	1.0 [ 12310154 ]
Fix Version/s	1.1 [ 12310346 ]
Fix Version/s		1.0 [ 12310154 ]

Jukka Zitting made changes - 13/Oct/06 04:07 PM

Status

Resolved [ 5 ]

Closed [ 6 ]

Jukka Zitting made changes - 07/Jul/09 01:04 PM

Workflow

jira [ 12351610 ]

no-reopen-closed, patch-avail [ 12469497 ]