New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exception message string issue #1

Closed
t106uhn opened this Issue Jul 18, 2014 · 1 comment

Comments

Projects
None yet
2 participants
@t106uhn

t106uhn commented Jul 18, 2014

Exceptions returned from the FHIR server contain the message string in the response body. On the client side, calling getMessage() on the exception only obtains minimal information (e.g. HTTP 500 Internal Server Error), the client needs to cast the exception to BaseServerResponseException and call getResponseBody and then navigate to the issue.details field to obtain the message string. It would be more useful to have the message string added to the message field in the Exception object. Most logging logic in java prints/logs data from the message field.

@jamesagnew jamesagnew added this to the 0.5 milestone Jul 22, 2014

@jamesagnew

This comment has been minimized.

Owner

jamesagnew commented Jul 22, 2014

Fix checked in

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment