Error information returned to web ui from jazz service
![](http://jazz.net/_images/myphoto/3ac04890783e92ebeb57343916d9fb09.jpg)
One answer
![](http://jazz.net/_images/myphoto/3ac04890783e92ebeb57343916d9fb09.jpg)
"fmcgrath" <fmcgrath@us.ibm.com> wrote in
news:fgt294$per$1@localhost.localdomain:
There are some discussion in the WebUI about how to return info to the
client... if you cannot find them, ping me :)
IMHO, 500 cannot be handled by the client - Is it really worth to send the
whole stack trace back ?
I suggested (but not yet implemented <hint hint>) that we catch the
exception, handle them in a common page and allow the user to notify the
admin (email, send info to rest service etc..)
Also, I believe there is a way to get the server log from a Rest service,
so if a user REALLY wants to see the log, we should be able, using the same
page, to call the service from the WebUi :)
--
Christophe Elek
Serviceability Architect
IBM Software Group - Rational
news:fgt294$per$1@localhost.localdomain:
All exceptions thrown in the server seem to return 500 errors to the
web ui. Is there a mechanism or recommended pattern to return more
information?
There are some discussion in the WebUI about how to return info to the
client... if you cannot find them, ping me :)
IMHO, 500 cannot be handled by the client - Is it really worth to send the
whole stack trace back ?
I suggested (but not yet implemented <hint hint>) that we catch the
exception, handle them in a common page and allow the user to notify the
admin (email, send info to rest service etc..)
Also, I believe there is a way to get the server log from a Rest service,
so if a user REALLY wants to see the log, we should be able, using the same
page, to call the service from the WebUi :)
--
Christophe Elek
Serviceability Architect
IBM Software Group - Rational