[XALANJ-990] QName.hashCode() inconsistent with QName.equals(Object)

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 2.4
• Component/s: Other
• Environment: Operating System: All; Platform: All
• Bugzilla Id: 8783
• Assignee: Unassigned
• Reporter: Achille Fokoue
• Created: 04/May/02 00:40
• Updated: 16/Feb/11 23:02

Description

Part of the general contract of hashCode() method is that "If two objects are
equal according to the equals(Object) method, then calling the hashCode method
on each of the two objects must produce the same integer result."
Unfortunately, this is not true for org.apache.xml.utils.QName. In fact,
QName.hashCode() is a function of its prefix, its namespace and its local name
whereas QName.equals(Object) is just a function of its namespace and local
name. This means that two QNames which differ only by their prefixes would be
considered equal but their hashCode values would be different( e.g. new QName
("http://examples.org","a", "example") and new QName
("http://examples.org","b", "example").
This inconsistency could lead to serious bugs if QNames are used as keys of
hash maps.