Hey

Aaron Mulder wrote:
>         Well, readin a little further, others seem to have come to the
> conclusion that your object is not fine, which the more I think about the
> more I agree with.  (Doesn't deserialization use a default constructor?)

No, serialization would be fine. But there's quite a few other things
that would be messed up. Each time you use the findByPrimaryKey method
for example you would be creating a new id.. just for *finding* another
entity..

>         But in any case, how do others thing about using a comparison of
> an object to its serialized and deserialized form instead of to a second
> object?  I guess it wouldn't catch situations like this, but it would be
> the "most accurate" test of whether equal objects are .equals().

It might be that, yes. It's a very minor difference though.

/Rickard

-- 
Rickard �berg

Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com



--
--------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Problems?:           [EMAIL PROTECTED]

Reply via email to