I learned I can track the root of any raised exception within Spring Web MVC by bypassing filters with the use of a class annotated with @ControllerAdvice and a corresponding method annotated with @ExceptionHandler and the desired exception to catch.
In the end, the issue's root cause was myself, sending invalid JSON (took me a whole hour to realize it! I blame Postman though).
Still, using said annotations helped me unveil how and where did my tests fail.
I'm a fan of Open Source and have a growing interest in serverless and edge computing. I'm not a big fan of spiders, but they're doing good work eating bugs. I also stream on Twitch.
I learned I can track the root of any raised exception within Spring Web MVC by bypassing filters with the use of a class annotated with @ControllerAdvice and a corresponding method annotated with @ExceptionHandler and the desired exception to catch.
In the end, the issue's root cause was myself, sending invalid JSON (took me a whole hour to realize it! I blame Postman though).
Still, using said annotations helped me unveil how and where did my tests fail.
Nice!