Looking through the 2.1.6 code, it appears that you can rely on
the values for the state parameters in the Interceptor methods
to always appear in the same order for a given entity. Is this just a
byproduct of the current code or is this intended?

thanks,

-r

What's the difference? You should be examining each entity in the array and acting on its state (or not) as desired.

For the current problem, I don't care what the state is. However,
I do care that any time the same entity is loaded from the DB, the
state array will look the same for each load. I want to generate a
checksum of the current state, so the order is important.

-r

This is intended. It is the same order as the mapping doc.

You could just alphabetize the properties (and keep track of their associated state), which will keep the order the same.

Yeah, ordering them would be easy, but I'm lazy. So, if I don't need
to order them myself, all the better.

-r

But, if at any time in the future, the order *does* change, you'll be wondering why your checksums don't work...

By the way, automatically computing a checksum on every row is a neat idea.

Yeah, but I'm not real concerned given Gavin's response, the Hibernate
code is pretty dependent on that ordering. I'm only making a short-term
fix anyway.



But it's problematic--throw collections in the mix and you get yourself
a tedious task.

-r