On Feb 24, 1:16 pm, David Chandler <[email protected]> wrote: > I see. I'm not a JPA expert
Nor am I, regrettably :) > > queryObject.setFlushMode(FlushModeType.COMMIT); This is what I've been considering, but it strikes me as an ugly solution, mixing data level considerations with business logic. But I'm starting to get the impression there's no easy way out of this. Once you use one EntityManager per request, you have write your application logic in full knowledge of the attendant limitations... -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
