commit 5f357893691ad268feab6c2374ab6311b5b1ed1a
author gwt.team.mmendez <gwt.team.mmendez@8db76d5a-ed1c-0410-87a9-c151d255dfc7> Mon Mar 10 04:38:19 2008 +0000
committer gwt.team.mmendez <gwt.team.mmendez@8db76d5a-ed1c-0410-87a9-c151d255dfc7> Mon Mar 10 04:38:19 2008 +0000
tree 46c1f7a320309d0c067f73836906f9c97aec3d76
parent 6876b7020daa04584f4a323c393f368a6cb3c6f1

Finishes issue 1139.  Adds java.io.Serializable to our JRE's version of Throwable.  The Throwable.getMessage() method for checked exceptions thrown by RPC methods no longer returns null if a user forgets to extend SerializableException.

The basic strategy is:

   1. Have the client-side code use Throwable's generated field serializer while the server special cases Throwable in its serialization/deserialization logic. 
   2. Only serialize the detailMessage field on Throwable.  The cause field was excluded because it could cause significant bloating of the client side proxy given the current setup of STOB.  The stack trace was not serialized because that does not seem like the type of information that you would want your clients to see.

SerializableException is now deprecated as since the detailMessage is now serialized by default.

Review by: Bobv

git-svn-id: https://google-web-toolkit.googlecode.com/svn/trunk@2047 8db76d5a-ed1c-0410-87a9-c151d255dfc7