I've noticed a few new additions to some of our remote GWT service
interfaces did not explicitly declare "throws RuntimeException"
If you ever add a method to a GWT interface, you must ensure it declares
at minimum a "throws RuntimeException". Otherwise, GWT won't be able to
send our exceptions over the wire and the user won't see any helpful
exception messages in the message bar or message center. All the user
will see is the nebulous "see server logs for the exception".
See:
https://bugzilla.redhat.com/show_bug.cgi?id=697559
I am in the process of adding the missing throws clause to the ones that
need it - all gwt interfaces will soon have throws clause. Any
additional ones you need, just make sure you keep with that design and
make sure you add "throws RuntimeException". You should also follow the
same design pattern as found in our *Impl classes that implement these
interfaces - that is, have a try-catch block that catches throwable, and
throw a cleansed exception so the gwt client can receive it and not
result in a serialization error.