You can call report() or die() depending on what you want to do. report()
re-throws a ReportableException while die() will re-throw an
UnexpectedException.
Also with your above implementation you are "hiding" the exception logic of
super.invoke() as it might also call report() or die() when it encounters
certain exceptions. I think a better implementation would be
@Override
public Object invoke(Method domainMethod, Object... args) {
try {
// some business logic such as check user role, etc.
} catch (Exception ex) {
// only catch exceptions from your custom code
// call report() or die()
}
return super.invoke(domainMethod, args); // assume super.invoke()
will do the right thing if it encounters exceptions
}
The generation of a ServerFailure is done in the DefaultExceptionHandler.
But you can also provide your own implementation by extending the
RequestFactoryServlet and provide your custom exception handler through the
constructor.
-- J.
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.
