directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <>
Subject [jira] Updated: (DIRSERVER-1516) Classes implementing compareTo should also implement equals (and thus hashCode)
Date Thu, 24 Jun 2010 12:02:51 GMT


Emmanuel Lecharny updated DIRSERVER-1516:

    Fix Version/s: 2.0.0-RC1

Scheduled to RC1, but can be finished on RC2

> Classes implementing compareTo should also implement equals (and thus hashCode)
> -------------------------------------------------------------------------------
>                 Key: DIRSERVER-1516
>                 URL:
>             Project: Directory ApacheDS
>          Issue Type: Bug
>         Environment: All
>            Reporter: Felix Knecht
>             Fix For: 2.0.0-RC1
> Following classes are lacking this problem
> [apacheds-protocol-dhcp]
> [apacheds-protocol-ntp]
> This class defines a compareTo(...) method but inherits its equals() method from java.lang.Object.
Generally, the value of compareTo should return zero if and only if equals returns true. If
this is violated, weird and unpredictable failures will occur in classes such as PriorityQueue.
In Java 5 the PriorityQueue.remove method uses the compareTo method, while in Java 6 it uses
the equals method.
> From the JavaDoc for the compareTo method in the Comparable interface:
>     It is strongly recommended, but not strictly required that (x.compareTo(y)==0) ==
(x.equals(y)). Generally speaking, any class that implements the Comparable interface and
violates this condition should clearly indicate this fact. The recommended language is "Note:
this class has a natural ordering that is inconsistent with equals." 

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

View raw message