...
From other hand the nature of a possible error (e.g. ) and the source module (the initial exception
is thrown from)
is quite variable. So it requires some unified and clear way for error information
delivery
from from service level (cps-service component) and below (e.g. persistence level). Also both
error message and error information delivery expected to be easily extendable.
...
To minimize the variety of cases to handle the project specific Exception to be introduced on
service level. The customer specific cases to be implemented via Exception inheritance.Summary:
cps-rest
- Error message model artifact - generated from OpenAPI spec on build
- error message builder - uses current module exceptions and the CpsException
(plus sub-types) returned thrown by cps-service
cps-service
- CpsExeption artifact as a part of SPI
To discuss/decide
- The Error message artifact vs OpenAPI - generated from or predefined (with annotation)
- Type of CpsException - checked vs unchecked