Hi,

I was wondering what the problem would be if Hibernate would pick up the Comparator instance (class) used for it's Set.

I have declared a Set like:




Because Hibernate replaces the SortedSet implementation with it's own, i lose the Comparator. This can as far as i see, only be resolved by setting the sort atribute on the set.




Are my assumptions right. If so why can't hibernate pick up the comparator from the initialized TreeSet before it replaces it.
If this can be done easier, please let me know as well.

cheers,

Raphael

Probably because H does not expect the field to be initialized on your class, it can be declared as
private SortedSet<Order> deals;
and H will be able to work,
http://www.hibernate.org/hib_docs/v3/re ... ons-sorted

Kind of make sense for me. Sensing current Comparator probaly is not a good idea because potentially somebody sets comparator at runtime and then spend days trying to figure out why mapping file specifies one sorting order and it is not working

Konstantin,

You are probaly right, but the other is true too (i went trough it ;) ): looking why the comparator just disapeared.

I guess the wise thing would be that Hibernate would generate a warning when it notices the developer initiliazes the SortedSet with a Comparator.

tx.,

Raphael

Just 2c:
My mental model of H is like this: H uses configuration file and static type information to take care of persistence. (Populate instance from database, “merge” instance and state). Therefore I do not think that H should introspect runtime state of an object and try to adjust own behavior to the state. I think it would be too much room for confusion.

In the end, it is up to H team to decide.