On Fri, Mar 6, 2009 at 11:10 AM, Rickard Öberg <[email protected]> wrote:
> That should not be a problem. When a nested UoW is completed the state > in the custom UoWEntityState is merged back by writing properties and > associations as if it had been done through application code. To the > underlying EntityState there is no difference. As above, the goal of > nested UoW is to "pretend" being application code as much as possible. I guess there is a lot of tests that we need to construct in this area. It is both essential to the overall system, as well as fairly complex semantics at play, so extremely important to deliver what we say. Cheers Niclas -- http://www.qi4j.org - New Energy for Java _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
