[
https://issues.apache.org/jira/browse/METRON-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15816622#comment-15816622
]
ASF GitHub Bot commented on METRON-503:
---------------------------------------
Github user jjmeyer0 commented on the issue:
https://github.com/apache/incubator-metron/pull/316
@merrimanr yes, I was thinking of something along these lines. At a high
level I was thinking that any exception that bubbled up through the controller
should be mapped to an error response. I believe Spring uses
`ResponseEntityExceptionHandler` to help with this
(http://docs.spring.io/spring-boot/docs/1.4.1.RELEASE/reference/htmlsingle/#boot-features-error-handling).
The benefits I see from doing this are keeping the error handling consistent,
separating concerns, and giving better feedback to the end user. It does
require more thought on what exceptions are thrown, and if the exception
handler has the ability to map them to a response . Does this make sense?
> Metron REST API
> ---------------
>
> Key: METRON-503
> URL: https://issues.apache.org/jira/browse/METRON-503
> Project: Metron
> Issue Type: New Feature
> Reporter: Ryan Merriman
> Assignee: Ryan Merriman
> Attachments: Metron REST API.docx
>
>
> As discussed on the dev list ([DISCUSS] Metron REST API Requirements), this
> Jira includes adding a REST API to Metron.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
