I just had to debug one of these errors.
I just set a break point where the exception is raised (i.e.
SerializerBase.java:161). I ran my app in debug developer mode and
when I hit the breakpoint I was able to inspect the parent call in the
stack where there is a method parameter called instance.
hi,
would not it be better to have a compilation error in such case, with
precise information like class and problem description??
see
http://code.google.com/p/google-web-toolkit/issues/detail?id=4828
regards
Michael
On Jun 3, 6:15 am, Sripathi Krishnan sripathi.krish...@gmail.com
wrote:
Greetings,
I'm having a frustrating time debugging a bunch of code I'm trying to
port to GWT. There are various subtle serialization issues (not
surprising, since GWT has its special rules).
The real problem I'm running in to is that the exception I keep
getting is this:
Confirm that all classes participating in RPC -
1. implement Serializable
2. have a zero-argument constructor
Most of the times I forget zero-argument constructor, and that's when I get
errors similar to what you have pasted.
--Sri
On 31 May 2010 20:23, svincent shawn.vinc...@gmail.com
