Thank you.
On Apr 20, 5:32 pm, Jens wrote:
> Take a look
> at:http://code.google.com/intl/de-DE/webtoolkit/doc/latest/tutorial/RPC
>
> J.
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to google-web
Take a look
at:
http://code.google.com/intl/de-DE/webtoolkit/doc/latest/tutorial/RPC.html#exceptions
J.
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubsc
No. Because doPost, which is what calls all our RPC code, throws
ServletException or IOException, and if you try to throw anything
else, Tomcat reports an error to its log about an unexpected
exception. Which is one of the things I dont' want.
Greg
On Apr 12, 12:04 pm, Christien Lomax
wrote:
>
In your service interface, declare that it throws one or more exceptions. This is what it
means to be a "recognized" exception. Also, make sure those exceptions are
GWT-serializable. You might want to create your own top-level exception for this, and
just declare that it throws that, but you d
I created an exception that my app uses (eg: MyAppException) that extends
serializable. Then when I need to throw an exception, I catch any other
exceptions and throw MyAppException instead, passing in the message from the
caught exception(s).
Make sense?
--
You received this message becaus
I'm trying to throw an exception from my servlet back to the client
without breaking anything along the way, and having no success.
First I was throwing an InvocationException, but this created an error
it was an unrecognized exception.
So I threw a ServletException. This is acceptable on the Se
