Spring 6 and Problem Details

This video shows how to use Spring Framework 6's new support for Problem Details (RFC-7807) to create clear and concise responses from an API when things go wrong.

If you want to learn more about developing with Spring and Spring Boot, check out my book, available wherever tech books are sold or specifically at either of these two URLs:

Or, for something completely different, have a look at my book on developing voice interfaces for Alexa:

If you enjoy this video, I'd appreciate a thumbs up! Leave me a comment and let me know what you think. And please, share with your friends and colleagues.

Thanks for watching!

[malliendk]

Very helpful and concise. Good way to stay updated. Good explaination of the project and the context, plus clear and easy-to-follow walkthrough taking us through all the steps necessary to succesfully implement this helpful feature ProblemDetail

[BusyAnt]

Good video, I did not know about the trick to have Spring default to ProblemDetails in case of "unpredictable" errors. As an addition, I believe it would have been helpful to mention the usage of the "type" field which is kind of central to the ProblemDetails concept. Everything is better than leaking the stack trace but "type" is really the identifier for the error and allows the clients to classify it as they see fit as well as providing them with additional information about the error over the URI.

[skies]

I remember when this Problem was part of zolando library and they had proper Spring integration. great to see that it is now a standard, thank you for the video.

[AlexK-vhwn]

Awesome, short and concise explanation. Thank you for spreading the knowledge!

[Anbu_Sampath]

Nice explanation about Problem Details feature.

[chinchi]

It would be very helpful if you could show the UnknownTeamException class. I'm new to Spring boot and some things are not obvious for me. Thank you very much.