Thank you very much Juan, you helped me finding an easier workaround. After seeing your use of filters to the RPC calls, I imagined there should be a way to filter the creation of properties in RequestFactory, and after searching a little I found that the ServiceLayerDecorator could help me if I just override the getProperty method. Much better now!
But I still think RF shouldn't visit all properties of an entity. Imagine how many people are using OpenSessionInView and are having unnecessary overheads in their applications without knowing. This could be done by just treating any Collection as a potential relation, and not even resolving the type of its members if this collection was not requested through with(). On Sep 9, 1:50 pm, Juan Pablo Gardella <[email protected]> wrote: > Hi Tiago, > > I use JPA2 (with Hibernate as a provider) in a GWT application. I use a > *Filter > *that put to null uninitialized properties in a transparent manner. So if > you in service layer don't initialize the properties, this filter solve the > problem of serialization. Check this > thread<http://groups.google.com/group/google-web-toolkit/browse_thread/threa...> > . > > Juan > > 2011/9/9 Tiago <[email protected]> > > > > > > > > > On Sep 9, 10:31 am, Thomas Broyer <[email protected]> wrote: > > > .with() has nothing to do with lazy-loading or "lazy initialization > > > exceptions"; it's only about what goes over the wire, and what's > > available > > > on the client-side. > > > Right, but if I haven't explicitly said that a certain property is > > going over the wire, then why is GWT accessing it with this > > AutoBeanVisitor? > > > > I don't know Gilead (and I actually don't use JPA or JDO, but if I had > > to, I > > > wouldn't use lazy-loading, it causes much more burden than what it's > > > supposed to "solve", it's not worth it, it's a lie, it's > > counterproductive > > > in the long run; JPA/JDO, like much "enterprisey" things, are > > > over-engineered and much too complicated to get them to work unless > > you're > > > an expert in the field). > > > You might have a good point there, but I'm not likely to remove > > Hibernate from this app. > > Many problems would be solved if Hibernate just automatically removed > > every instrumentation it does on entities after they're detached. I > > asked about Gilead because apparently that's what it does, but I > > haven't found any examples of somebody mixing Gilead and RF. > > > Thank you, > > Tiago. > > > -- > > 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. -- 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.
