Matt,
<vendor>
This is a very reasonable suggestion, and I have put a feature request
in for this. Thanks.
</vendor>
Others,
My apologies if you feel that I insulted you by saying that I don't trust
developers to write hashCode/equals correctly. Unfortunately, as an AppServer
vendor, we have to assume that some of our customers may be less advanced
than others, and that some of our customers may not know how to write these
methods correctly. It is our job to be able to run these beans efficiently,
IMO, even if the hashes are non-uniform.
-jkw
Matt Kleiderman wrote:
>
> Telling whether or not a developer has altered hashcode()/equals() strikes
> me as fairly time consuming. Telling whether they've done it "correctly"
> strikes me as impossible. If I were to make a suggestion for the next
> version I would recommend that it be part of the deployment descriptor
> whether to use hashcode()/equals() or a serialized PK class. This way you
> can even check if you've implemented hashcode()/equals() correctly by
> changing the setting and seeing if your application blows up......
>
> Cordially,
> Matt Kleiderman
> PfN, Inc.
>
> >
> >Jon,
> >would it not have been more powerful to defer to "user provided method" if
> >available else use internal comparison? Could you explain why this was not
> >your preferred approach...
> >/Deepak
> >
> ><snip>
> >
> >On the other hand, you might argue that we are not compliant with the EJB
> >specification, in that we do not use on the user's implementation of
> >hashCode
> >and equals (bugs and all), but instead use serialization for comparison
> >purposes. (I don't see anything in the spec to preclude what we do, of
> >course.)
> >
> ><snip>
> >
>
> ===========================================================================
> 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".
