Order of sub-editor setters in RequestFactoryEditorDriver
I am creating a RequestFactory context by calling edit() on a proxy
(which contains sub-proxies).
I have an editor for the proxy (with sub-editors for the sub-proxies).
Call this proxy the "top-level proxy"
The editor framework automatically calls context.edit() on any sub-
proxies it encounters (which is helpful); however, this means when the
driver is flushed, the setters for the top-level proxy are called
first, followed by its children's setters, and so on. So when I use
the default editor framework behavior, my top-level proxy proxy will
never accurately reflect the editor changes.
Do I really have to manually call edit on all my sub-proxies in a leaf-
first way in order to get the behavior I need? Shouldn't the driver
do it that way be default?
Or am I thinking of this incorrectly?
--
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-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
0 Comments:
Post a Comment
Subscribe to Post Comments [Atom]
<< Home