Oh, and EntityBaseProxy is simply the following at the moment:
public interface EntityBaseProxy extends EntityProxy {
public String getId();
}
On Jan 23, 2:15 pm, RyanD <[email protected]> wrote:
> Absolutely:
>
> ---
> @ProxyFor(File.class)
> public interface FileProxy extends EntityBaseProxy{
> public String getPath();
> public void setPath(String path);
> public String getContentType();
> public DefinitionFileDataProxy getData();
> public void setData(DefinitionFileDataProxy data);
>
> }
>
> @ProxyFor(FileData.class)
> public interface FileDataProxy extends ValueProxy {
> public String getTextData();
> public void setTextData(String textData);}
>
> ---
>
> As mentioned, I am able to successfully "edit" other properties such
> as "File.path" clear through to server side, which is why I'm focusing
> on the ValueProxy.
>
> Anything useful gleaned there?
>
> Thanks,
>
> Ryan
>
> On Jan 23, 1:37 pm, Thomas Broyer <[email protected]> wrote:
>
>
>
> > Looking at AbstractRequestContext, it looks like you don't have to
> > explicitly .edit() ValueProxy-s if you .edit()ed the containing EntityProxy
> > (or ValueProxy), so scenarios 1 and 2 would be identical (and
> > req.edit(file.getData() should be == file.getData()).
>
> > As SrArcos already asked, could you show us the code of your proxies?
--
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.
