That's the behavior I'd expect too. This did work at one point. No, it's not unintuitive. Least not for C programmers :-)
But I've got smoking gun evidence though that's not what's happening. I'm now wondering what's happening in these setters...
Tx for making sure I wasn't spacing.
um. maybe you are? ;-)
You wrote:
> >I call PropertyUtils.copyProperties(user, userEntity) and I'm watching a> reconstructed).map >that was an element of the user object (and not of the userEntity) getting >blown away (almost as if the User Object itself was getting
I wrote:
> So, by your example, user should be having all its properties set > according to their equivalent values in userEntity.
user is having its properties set -- it is getting reconstructed -- because you have it in the first position, the "destination" position.
If you want to populate the UserEntity, you should use
PropertyUtils.copyProperties(userEntity, user)
which is the opposite of what you're saying that you are using.
Joe
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Narrow minds are weapons made for mass destruction" -The Ex
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
