great! I'm still evaluating RequestFactory, maybe requestContext.isChanged() is what I'm looking for.
Thanks, Fábio. On 17 nov, 12:31, Thomas Broyer <t.bro...@gmail.com> wrote: > On 16 nov, 19:34, Fábio Miranda <fa...@miranti.net.br> wrote: > > > Hi, > > > Is there any way to check if an editor/object states has changed, > > something analogous to flush method, but without generating errors and > > making changes to the object? > > No, the driver is "dumb", it only (and that's already a big time- > saver) "copies" from the edited object into the editors (when calling > edit()) and back from the editors to the object (when calling > flush()). > > > An workaround can be Editor making a object copy to driver edit, flush > > driver on that copy, and than compare the flushed copy with the > > original object, but could be simpler if driver could check this > > automatically for us... > > That's what we're planning to use (given that our team chose –to my > great regret– to go with GWT-RPC rather than RequestFactory: > RequestFactory's RequestContext have an isChanged() that you could use > after a call to flush() to know whether the edit()ed objects within > that context have changed) -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
