Using of @ControllerAdvice as an idea - it's ok. But the problem of Spring' implementation is that there could be only one @ControllerAdvice with @ExceptionHandler ((. So, this class become really huge (from the responsibility point view, of course).
Using of @ControllerAdvice as an idea - it's ok. But the problem of Spring' implementation is that there could be only one @ControllerAdvice with @ExceptionHandler ((. So, this class become really huge (from the responsibility point view, of course).
yes that is certainly a downside