db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Bouschen (JIRA)" <j...@apache.org>
Subject [jira] Closed: (JDO-109) Need better information about why two object graphs did not compare equal
Date Sat, 22 Apr 2006 19:48:21 GMT
     [ http://issues.apache.org/jira/browse/JDO-109?page=all ]
Michael Bouschen closed JDO-109:

    Fix Version: JDO 2 beta
     Resolution: Fixed

> Need better information about why two object graphs did not compare equal
> -------------------------------------------------------------------------
>          Key: JDO-109
>          URL: http://issues.apache.org/jira/browse/JDO-109
>      Project: JDO
>         Type: Improvement

>   Components: tck20
>  Environment: TCK
>     Reporter: Craig Russell
>     Assignee: Craig Russell
>     Priority: Minor
>      Fix For: JDO 2 beta

> Need better reporting of deep equality failures. 
> During completeness testing, if two object graphs are compared and the result is that
they are different, there needs to be more information about exactly what is different between
the object graphs.
> The methods in each class deepCompareFields need to be changed to call into the EqualityHelper
to do the comparisons and the EqualityHelper can report inequalities if the fields don't compare.
During the comparison process, all fields need to be compared, and the results of compare
need to be recorded by EqualityHelper. After the comparison of the graph, the collected information
can be dumped if the results are "not equal".
> New methods in EqualityHelper that take a String tell which fields of which class are
being compared. Each of the equals(o1, o2) and closeEnough(o1, o2) methods need to be expanded
to include a third parameter which tells which field is being compared. If the result is unequal,
then the field information is saved in a StringBuffer to be returned if the result of the
entire comparison is "not equal".

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message