commit 17c9313c29bf7eb5f6cd2fbc2d79004b39391eeb
author scottb@google.com <scottb@google.com@8db76d5a-ed1c-0410-87a9-c151d255dfc7> Wed Nov 24 17:30:26 2010 +0000
committer scottb@google.com <scottb@google.com@8db76d5a-ed1c-0410-87a9-c151d255dfc7> Wed Nov 24 17:30:26 2010 +0000
tree 3e158f0b5bc48b585bc2c7f11ab5740b8506309e
parent 24fef3e9f34d2bcd879d3d3a7ee0cd46dbf591df

Fix to allow devmode exceptions to be reported back from a client.

When I converted JUnit to use normal serialization to transmit exceptions, I introduced a problem.  In DevMode, exceptions can get into the client space from the hosting environment, such as HostedModeException.  Because these types are not visible to the client, they can't be serialized.  This works around the issue by using a known-good exception type.

http://gwt-code-reviews.appspot.com/1147801/show

Review by: conroy@google.com

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