the stack trace says it all....
there is no way for hibernate to figure out the unique rows from a joined resultset with multiple bags.
Thus instead of creating duplicate entries in your llist we fail with the stacktrace.
In the future we plan to provide a fallback for this scenario where a second (sub)select will be done to load the other bags.
Hmm, the attributes Customer.orders and Order.shipments are annotated with
I thought that bags can be avoided this way.
but your Orders is a List, right ?
Yes, both "orders" and "shipments" are of type List<>.
Will adding @IndexColumn solve the problem?