We tried that and it works as said in my previous post: the presence of class A in the method signature is enough to make it required. Actually, the same applies to mere transient fields: even if the field is transient and doesn't have a getter/setter, the class is still required... Quite disappointing honestly!
On 14 Gen, 14:12, Chris Lercher <[email protected]> wrote: > I'm not so sure about that. If your client never uses the getter/ > setter, it can (theoretically) be pruned. The reason such pruning > cannot be done with a non-transient field is that this would incur > data loss (when sending the object back to the server).
-- 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.
