On Friday, June 14, 2013 8:03:57 PM UTC+2, Yan wrote: > > Hi, > > With my GWT 2.5.1, I am revisit the way I am using EntityProxy. There is > an existing post about a parent entity proxy holding a list of children > entity proxy, changes in children in UI does not trigger an update in > backend. > > So, I thought to change to use ValueProxy, that way, I do not have this > problem, as everything is sent to server. There is not that much data, so > it won't be a performance problem. > > But, is not using AutoBean more straightforward? Just define an > interface, both client/server are serializing and unserializing the objects > into JSON string. > > Is ValueProxy essentially the same as object being serialized using > AutoBean? >
If you don't need/use the other features of RequestFactory (batching, graphs that reuse the same object several times, bean validation, EntityProxyChange event, polymorphism) then yes. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/groups/opt_out.
