[
https://issues.jboss.org/browse/SRAMP-129?page=com.atlassian.jira.plugin....
]
Eric Wittmann resolved SRAMP-129.
---------------------------------
Resolution: Done
Formalized the error handling a bit. Every exception thrown by the
s-ramp server is now either a user exception or a server exception. All
exceptions are returned to the client in the response, but only server
exceptions are logged.
Be more selective about what errors get logged by the server
------------------------------------------------------------
Key: SRAMP-129
URL:
https://issues.jboss.org/browse/SRAMP-129
Project: S-RAMP
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Kurt Stam
Assignee: Eric Wittmann
Fix For: Milestone 3 (Workflow and Relationships)
There are a few stacktraces when running the test. We should change our code to make sure
we don't show stack traces if there is no true exception.
In general, this means we should be able to tell the difference between a hard server
error (ioexception, modeshape blew up exception, etc) and a "user" error
(invalid s-ramp query syntax, uuid not found, etc).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira