Unless it's one of a couple types of errors we
"expect" to see during
runtime, Cosmo UI's error reporting is not very helpful -
you usually
just see "Could not Load Events" or "Could
not Save events".
Back in the JSON-RPC days we had the ability for users to
optionally
view the Java stack-trace via a "details" button.
Nowadays we don't
get Java stack traces anymore but we do get plenty of
information
back from the server that we're not displaying - namely, the
Error
code, the response HTML, etc.
I'd like to see that nice details button repurposed to
display this
information.
The way I'd like to see this done is for Errors to have a
"toStringVerbose()" method which would display
lots more information
Ideally I'd like to get this done really soon, like within
day or so,
because I think it would really help testing. Far too often
someone
reports a bug and we have no way of knowing what kind of
Error was
thrown - this happened to me and Aparna today and I was
incredibly
frustrated that I had no way of knowing what has going on.
Unless
anyone objects, I'm going to invest a couple of hours making
this
happen, especially now during bug hunting season.
bobby
_______________________________________________
cosmo-dev mailing list
cosmo-dev lists.osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo-d
ev
|
