Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/GEOS-170
Here is an overview of the issue:
---------------------------------------------------------------------
Key: GEOS-170
Summary: User config option for stack traces in responses
Type: Improvement
Status: Open
Priority: Minor
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: GeoServer
Components:
Error Reporting
Fix Fors:
1.2.1
Versions:
1.2.0-rc1
Assignee: Chris Holmes
Reporter: Chris Holmes
Created: Fri, 4 Jun 2004 12:49 AM
Updated: Fri, 4 Jun 2004 12:49 AM
Description:
Paul had Richard fix errors on geoserver so they don't look as if the server kacked - that is they just return the message instead of the full stack trace. I think this is a good default, but I'd like to see the option configurable, as the option to see the stack trace right there is quite useful from a developer's perspective, as the users don't have to dig through error logs, it's right there for them to see. It should not be too difficult to make this a user config option.
And the error reporting needs to be cleaned up, it is a bit inconsistent, it still occasionally performs full stack traces. I'm pretty positive that SAXExceptions will do this, among others. So we need to make sure that all exceptions perform the same behavior.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira