>
> re. Is it documented anywhere?
>
See GWT Presentations page -
http://code.google.com/webtoolkit/media_gallery.html. The Story of Your
Compile presentation explains this, and a lot of other optimizations.
Other than that, I am not aware of any other documentation.
--Sri
On 13 April 2010 15:
aha, that is helpful. I didn't know about the existence of the
{App}.rpc.log file (is that documented anywhere?)
for anyone reading this who isn't aware, this log file is presumably
created as the compiler works out what types are reachable and whether
they are serializable and goes something lik
Yes, T must extend a serializable type, as you said otherwise GWT
can't tell what it might be. Yes serialization discovery issues are a
pain...right now you just have to stare through the RPC log and try to
divine what happened.
On Apr 12, 4:46 am, Jon Vaughan wrote:
> I think the problem is tha
I think the problem is that on this example the type of the payload
can be anything (it is not required to be serializable); given that
this is possible, GWT must say, OK, then this type itself cannot be
serialized (I would like this to fail the compile though somehow)
On Apr 12, 10:27 am, Jon Va
Hi,
I have a serialization issue to solve, where a class that is passed to
the client, and is marked as IsSerializable, with a default no arg
constructor, does not end up in the whitelist. There are no messages
during the gwt compile (at debug level)
1. Does anyone have any thoughts about how I
