Cyclic dependencies in hashCode and toString implementations in some API objects

12060
Reporter: lfrancke
Type: Bug
Summary: Cyclic dependencies in hashCode and toString implementations in some API objects
Priority: Critical
Resolution: Invalid
Status: Closed
Created: 2012-10-22 17:42:13.098
Updated: 2013-12-06 13:18:49.703
Resolved: 2013-12-06 13:18:49.667
        
Description: At least the registry API part has cyclic dependencies in toString and hashCode

Some classes involved are: Agent, Contact, MetadataProperty, TechnicalInstallation.

This means we can't use these classes in HashMaps or for logging. I expect this is only true in some cases (certain fields populated etc.) but it is still very critical.

I think we should go through all of our API and come up with a proper equals, hashCode and toString hierarchy and implementation. This might be harder now due to all the inheritance.]]>
    

Author: fmendez@gbif.org
Comment: This was Registry 1.0 issues
Created: 2013-12-06 13:18:49.701
Updated: 2013-12-06 13:18:49.701