Hi,
the RPC.java has a method public static String
invokeAndEncodeResponse which does catch an InvocationTargetException
and tries to encode the error.
Here a snippet:
catch (InvocationTargetException e) {
// Try to encode the caught exception
//
Throwable cause = e.getCause();
responsePayload = encodeResponseForFailure(serviceMethod, cause,
serializationPolicy, flags);
}
return responsePayload;
The disadvantage is that the information about the exception is
actually in e.getTarget. As a consequence no detailed are carried to
the server. It indicates the normal "error on server" message.
e.getCause is null.
Is there any motivation behind using the e.getCause or is this
actually a bug.
Best Regards
Sebastian Hennebrueder
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
