Exception handling in Caching Service #4426
Description
This issue is based on #4408
Almost all exception thrown in the Caching service uses class StorageException. This exception means a state or it is used just to wrap original exception. All the exception are handled in the controller and there is no ControllerAdvice bean. All this complicates the control of program. It is very dificult to decide what error message should be returned. It the PR #4408 is possible to look what is the temporary solution of this issue. Anyway, the aim of this issue is:
- separate exception handling to a new class (ControllerAdvice)
- create a structure of exception that allows to easily detect reason of failure
- review the whole Caching service and caller part in the Gateway on how exception are handled
- write multiple tests to verify if the proper response code was returned