On 16. nov. 2010, at 11:01, Rickard Öberg <[email protected]> wrote:
> On 2010-11-15 12.22, Ronnie Nessa wrote: >> Hi. >> >> I found another possible bug in the UnitOfWorkCallback handling code. I >> don´t have time to write a testcase now, so I´ll try to explain it. >> >> Problem: >> >> If an entity which implements UnitOfWorkCallback loads any entities in >> the callback method which haven´t already been loaded into the current >> unit of work (either by traversing an association that is lazy loaded or >> by directly loading other entities by other means) it leads to a >> java.util.ConcurrentModificationException in the notifyBeforeCompletion >> method of UnitOfWorkInstance. > > What code is it that raises the CME? Is it the EntityStore or the UoW? > > /Rickard > > It's the iterator in the inner abstract class ForEachEntity in UnitOfWorkInstance, around line 509 depending on which version your code is at. It happens when notifyAfterCompletion is called. Does that help? > _______________________________________________ > qi4j-dev mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/qi4j-dev _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
