Hello all, I'm having a weird scenario in my application, and I guess that if I could understand better how RF picks the domain objects instances it will provide to a service, maybe I could understand what's going on.
Here's my scenario: I have an Editor<AProxy>. The domain class A has a property B which is another domain entity. In the editor there's a ValueListBox<BProxy>. Use cases: * If I just load the editor and hit submit without touching anything, everything works nicely. * If I change the value of B by picking another entity in the ValueListBox, it also works nicely. * If I change the value of B as above, but before submitting I change my mind and return the ValueListBox to its original value, RF will send to my service an object A whose property B is a non-initialized Hibernate proxy, linked to a closed session. That will result in a LazyInitializationException. In the other two cases, it was sending me an instance of B, not a hibernate proxy. Can somebody kindly help me understand how RF composes my object A after receiving the request payload? Where is it getting this uninitialized proxy from? Thank you, -- Tiago Rinck Caveden -- 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.
