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?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
