> I can see the merits of Inprise alleviating the burden of Java developers > having to implement these 2 functions by using the serialized bytes of a pk > object to intrinsically implement hashCode and equals. However, one can > also argue that you have stripped a power user the ability, even the option, > to define how she wants to do equality and hash comparisons! And I think > that's what the creators of Java intended: to allow users to implement > these two functions so they can define the way they want objects to behave > in a hash container such as HashMaps and HashSets, and in our case, EJB Key > comparisons! I agree whole-heartedly with Gene on this point. I totally despise a vendor taking options away from me on the assumption that I am too stupid to properly implement a piece of code. Often, it is not this insult which is the problem, but precisely what Gene has run into. The developer wants/needs control that is not available. I am all for a vendor implementing things, as long as there are proper hooks that allow me to get back control. tim. =========================================================================== 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".
