-
Task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
33
-
Not defined
Context:
We throw a lot of exceptions for different cases (sometimes on no result, sometimes on actual communication errors) on the reader level which makes it very intransparent what happens if you use methods from the reader layer. To avoid that we started to use Optional objects.
AT:
- the reader layer only throws exceptions on communication problems with the soure (elasticsearch)
- in cases where there was just no result (e.g. by id not found) it returns Optional wrapped dto's to signal this rather then throwing e.g. Rest Exceptions like notFoundException
This is the controller panel for Smart Panels app
Align error and no result handling in reader layer
-
Task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
33
-
Not defined
Context:
We throw a lot of exceptions for different cases (sometimes on no result, sometimes on actual communication errors) on the reader level which makes it very intransparent what happens if you use methods from the reader layer. To avoid that we started to use Optional objects.
AT:
- the reader layer only throws exceptions on communication problems with the soure (elasticsearch)
- in cases where there was just no result (e.g. by id not found) it returns Optional wrapped dto's to signal this rather then throwing e.g. Rest Exceptions like notFoundException
This is the controller panel for Smart Panels app
- mentioned in
-
Page No Confluence page found with the given URL.