We are using the following approach.
1 - On serverside, MyException is generated as we generate any other
exception
2 - On Frontend, get the message using myExcepiton.getExcMessage();
Let me know if it help.
+Bakul+
public class MyException extends Exception implements IsSerializable
{
private static final long serialVersionUID = -3821801999548017773L;
private String excMessage;
public MyException () {
}
public MyException (String message) {
super(message);
excMessage = message;
}
public MyException (Throwable cause) {
super(cause);
}
public MyException (String message, Throwable cause) {
super(message, cause);
excMessage = message;
}
public String getExcMessage(){
return excMessage;
}
}
On Sep 29, 10:18 am, Andrey <[EMAIL PROTECTED]> wrote:
> Hello!
>
> When an exception is thrown on server while handling RPC call, I set
> its cause to informative exception (i.e. database exception) and I
> want to use this information on client.
>
> While on server I can see the cause and print it, but when exception
> gets to the client cause is set to null !
>
> Why isn't exception cause serialized along with exception message and
> stack trace?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---
