entirely correct, but what has that got to do with the correctness / incorrectness of handing exceptions in a component instead of a container? I think you missed my point.
-Enda. ----- Original Message ----- From: "Cedric Beust" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, June 25, 2002 3:12 PM Subject: Re: hashcode and equals method > > From: A mailing list for Enterprise JavaBeans development > > [mailto:[EMAIL PROTECTED]] On Behalf Of Enda > > > Exceptions are not thrown to be caught and hidden away from > > console screens, they are there to tell you that somthing has > > gone wrong. > > This is true in general but incorrect for equals(). > > The contract of equals() is crystal clear: if the objects are > identical, return true, otherwise return false. > > If I compare an AddressPK with an EmployeePK, the result should be > false. Anything else, even an exception, is a breach in the contract of > equals(). > > -- > Cedric > > ====================================================================== ===== > To unsubscribe, send email to [EMAIL PROTECTED] and include in the body > of the message "signoff EJB-INTEREST". For general help, send email to > [EMAIL PROTECTED] and include in the body of the message "help". > > > =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
