When to use ValueProxy vs. EntityProxy
Hi there,
I thought that if I want GWT only send delta changes to server, then EntityProxy is a better fit.
I just realized that EntityProxy is also a better fit if you do not want you persistence layer load the entire object tree (ends up loading too much data in server) every time you ask for the top level object.
With GWT 2.5, I declare all my data objects are value proxy with JPA relationships set up on server side. I noticed that, even with LazyLoading setup in JPA, the server is still loading everything. This is because GWT is traversing all properties on a the class implementing ValueProxy interface and loads every property. Is that correct?
Thanks,
Yan
-- 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 google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
0 Comments:
Post a Comment
Subscribe to Post Comments [Atom]
<< Home