Hi, I now get many deserialize issues in GWT 2.0 that did not popup before.
It happens when I have an exception that chains exception types that are not handled by GWT. I used to be ignored since the root exception was correctly propagated. But now my RPC calls fails with a deserialisation problem. Is there a way to interfere (in a supported way) with the serialisation of Exception classes so that the cause is not serialized when it is not compatible with GWT ? In most cases I am only interested in the toplevel exception. So I rather implement a workaround than fixing all code. I rather log/trace the places where these problem arrise instead of halting the application completely. David
-- http://groups.google.com/group/Google-Web-Toolkit-Contributors
