> I believe you have to .edit() the FileData, as in the second scenario.
Tried that -- produces the same null result via logging. Not sure what's going on here. I may push forward with your second suggestion and ditch the ValueProxy for now. Perhaps by the time I truly need a ValueProxy there will be an example or insight into why this isn't working. Thanks for your thoughts. Ryan On Jan 23, 11:13 am, Thomas Broyer <[email protected]> wrote: > On Sunday, January 23, 2011 5:53:46 PM UTC+1, RyanD wrote: > > > SrArcos: FileData is a simple ValueProxy. It is just a wrapper > > around a potentially large String so I can easily include / exclude it > > from certain requests. > > Depending on the exact use case, note that you can also do this by listing > in a .with() all properties you do want (excluding the "potentially large > String" property when not needed). If you're using the Editor framework, > it's a no-brainer: just use the RequestFactoryEditorDriver's getPaths() > method. > > > Thomas: I retried the first scenario (above) with additional logging: > > > - First: file.setData(..) is called first by GWT. It is passed an > > instance of FileData. > > - Second: fileData.setTextData(...) is called by GWT on the instance > > it just passed to file.setData(..). However setTextData is passed a > > null String value. > > I believe you have to .edit() the FileData, as in the second scenario. -- 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.
