I'm not sure about this one, but basically I do know that the GWT RPC
mechanism needs to know if your RPC services are planning on throwing
an exception. In my code I have the following:
public interface UserService extends RemoteService {
void save(User user) throws ServerSideException;
}
If I don't specify throws ServerSideException then I get "Call failed
on the server; check server logs", if I do add throws
ServerSideException I get control of the exception and I can give it a
meaningful message. I'm not sure that this is exactly what you are
facing though?
Paul S
On Feb 20, 11:42 pm, bhomass <[email protected]> wrote:
> I got my server side code to throw custom exceptions for a long time
> and have a lot of working code to copy from.
>
> this time, I throw a ExpiredSessionException, it got translated to
> StatusCodeException. and on the client side, caught.getMessage() is
> this huge html fragment, starting with Http Error: 500. the whole
> message is too big to display in the error dialog and is unsuitable
> for users.
>
> the only difference I can detect is
> 1. the ExpiredSessionException is not a declared exception,
> 2. it is throw during the service() call, instead of in one the rpc
> methods.
>
> I am not sure what is the cause for loosing my original Exception.
>
> how can I get gwt to throw my own exception and not the
> StatusCodeException?
--
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.
