I'm working on a fix right now. I think fixing it is easy-- writing the test is a little more work.
john -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, July 03, 2002 9:03 AM To: [EMAIL PROTECTED] Subject: RE: Is this a bug in serialization? If serialization is using the hashcode method to determine whether two references are the same object, this is definitely a bug. Please open a Bugzilla defect. The hashcode and equals methods are great for what they were designed to do...but no more. The generated equals method defines equality by applying equals to each property (note this is not the same as identity equals). The hashcode method determines a hashcode based on the hashcodes of each property (again this is not an identity hashcode). Note that the hashcode method must return the same value for two objects which equals() defines as true. In most cases this kind of equals() is more valuable than identity equals. However if you need a different version of equals you will need to write your own or delete the existing methods. Just make sure that you keep equals and hashcode in sync. Thanks, Rich 'Shirley' Scheuerle IBM WebSphere & Axis Web Services Development 512-838-5115 (IBM TL 678-5115)
