As a developer I'd like to define the exception handling strategy for the Parodos RESTful service (workflow, notification) so that exceptions/errors occurring while processing requests including constraints violation (DTOs, entities, business/domain rules, etc...) should be caught and processed gracefully to return meaningful information the caller/user such as HTTP status, error message, etc.
AC:
- Review REST API exception handling best practices and make a proposal for Parodos REST APIs.
- depends on
-
FLPATH-333 Use hibernate validator for request parameters
-
- Closed
-
- is related to
-
FLPATH-341 Add constraints on model entities
-
- Closed
-