Let me see if I get this right... In this example there is obviously
no closed cycle. So you are saying AshwoodEntitySorter still assumes
there is one, and gives up on ordering? Then this is a bug.
Andrus
On Jul 10, 2009, at 11:20 AM, Andrey Razumovsky wrote:
> Imagine references avaliable A->B->C->A
>
> 1. Create dependant entity B
> 2. Create master entity A
> 3. b.setA(a)
> 4. Commit.
>
> C is even never used.
This archive was generated by hypermail 2.0.0 : Fri Jul 10 2009 - 04:32:13 EDT