[
https://issues.apache.org/jira/browse/QPID-7908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7908:
-----------------------------
Fix Version/s: Future
> [Java Broker, REST] Improve exception handling and error reporting in web
> management
> ------------------------------------------------------------------------------------
>
> Key: QPID-7908
> URL: https://issues.apache.org/jira/browse/QPID-7908
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Affects Versions: qpid-java-6.0, qpid-java-6.0.1, qpid-java-6.0.3,
> qpid-java-6.0.4, qpid-java-6.0.5, qpid-java-6.0.6, qpid-java-6.0.7,
> qpid-java-6.1, qpid-java-6.1.1, qpid-java-6.1.2, qpid-java-broker-7.0.0,
> qpid-java-6.1.3, qpid-java-6.1.4, qpid-java-6.0.8
> Reporter: Alex Rudyy
> Fix For: Future
>
>
> Exception in web managements are handled in multiple places:
> * RestServlet itself
> * ExceptionHandlingFilter
> * HttpManagement$ErrorHandler
> Exception handling in RestServlet results in json response generation with
> error details, but exception handling in ExceptionHandlingFilter and
> HttpManagement$ErrorHandler does not produce the json response. As result,
> REST client can receive empty response claiming to be application/json or
> text/plain response, when valid application/json response is expected.
> We need to improve the exception handling and generate application/json
> response with error details for any REST application/json request.
> Additionally we can formalize and improve the format of the response with
> error details. At the moment, out response consist of errorMessage field.
> Potentially, we can improve the error response format that follow some of
> common practices for errored responses.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
