I believe RF is not meant to be used with lazy-loading if you don't also use (and accept the consequences) "OpenSessionInView".
If you detach your objects "early", then you have to either remove the lazy-loading (best IMO, lazy-loading is appealing but the risks of loading much more than needed, generally in hard-to-debug places, and the hard-to-optimize –when possible, 'cause you'll generally design your services in such a way that lazy-loading is implied, with no hook to eager-load the things you need– requests are not worth it; I'd even go as far as saying that the benefits of JPQL are a lie, but that's another story) or "unproxy" your objects rather than simply detaching them. See http://stackoverflow.com/questions/3642151/detach-jpa-objects-with-lazy-initialized-properties and http://stackoverflow.com/questions/5350485/how-can-i-determine-whether-hibernate-has-lazy-loaded-the-proxy-or-the-real-obj -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/dsdb2Y4yFTwJ. 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.
