On Tuesday, June 12, 2012 5:31:01 PM UTC+2, Thomas Broyer wrote: > > See > http://code.google.com/p/google-web-toolkit/wiki/RequestFactoryMovingParts#Flow > for > details on how a request is processed. The B domain object is > created/loaded in the “All domain objects referred to by the payload will > be loaded.” phase, that is, the very first thing that's being done on the > server to process the request. >
I don't understand how is this property loaded. Why when I change it to something else (case 2), an actual instance of my entity is loaded, but when I change to the same thing, an uninitialized Hibernate proxy is loaded? The locator linked to the proxy interface via the @ProxyFor annotation is set to always load initialized instances. (Session.get(Class, Serializable) method in Hibernate is used). Do you know where is this Hibernate proxy coming from? > If you used OpenSessionInView though, it would just work; it would do > some unnecessary work, but it would work. > Why? My "UI Service" (the @Service behind the RequestContext) passes entity A as it receives it to the in-session service which actually have the exception. It is not touched by the UI service code, only in the business service layer the entity is touched. Thank you a lot! -- 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/-/KNniFRh70k0J. 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.
