Let's say in my service class, I'm doing multiple operations to return something to controller. Out of those many operations in service, i may get 10 different exceptions, so do i need to catch specific exceptions or directly catch generic exception in service and throw our custom exception, so that even we don't handle specific exception or anything in controller, restcontroller advice catches our custom exception
Great question! It's a good practice to catch specific exceptions as much as possible in your service layer, as it gives more clarity on what went wrong and helps you handle different scenarios appropriately. However, if you have several different exceptions, you can group them and map them to a custom exception, which can then be handled by the @ControllerAdvice. For example, you could catch specific exceptions like NullPointerException, IllegalArgumentException, etc., in your service, then wrap them in a custom exception (e.g., CustomServiceException). This custom exception can be handled centrally in @ControllerAdvice. Catching a generic Exception directly in the service might hide the actual problem, making debugging difficult. Always try to handle known exceptions first, then fall back on generic handling if necessary. This way, your @ControllerAdvice can consistently handle the custom exception and return a proper response to the client.
How much time to enough to learn spring boot from scratch? And what should I need to learn for 2 to 3 year experience person . Earlier worked on core java and SQL .please guide me
Truly helpful, cleared all my doubt about the necessity of this global exception handler. Thanks and keep growing 😊
Thanks 🙏 Glad it helped
I sreached many videos but this is truly helpful, very clearly explained thank you💐
Thanks 🙏
Great Content bro, where are u from so many days youtube is doing wrong with u you should be top of all tutor
Thanks bro 🙏 Keep supporting ❤️
Very much Helpful.
Thanks 🙏
Bro please make a video on Aunthentication and jwt 0:19
Sure
Let's say in my service class, I'm doing multiple operations to return something to controller. Out of those many operations in service, i may get 10 different exceptions, so do i need to catch specific exceptions or directly catch generic exception in service and throw our custom exception, so that even we don't handle specific exception or anything in controller, restcontroller advice catches our custom exception
Great question! It's a good practice to catch specific exceptions as much as possible in your service layer, as it gives more clarity on what went wrong and helps you handle different scenarios appropriately.
However, if you have several different exceptions, you can group them and map them to a custom exception, which can then be handled by the @ControllerAdvice.
For example, you could catch specific exceptions like NullPointerException, IllegalArgumentException, etc., in your service, then wrap them in a custom exception (e.g., CustomServiceException). This custom exception can be handled centrally in @ControllerAdvice.
Catching a generic Exception directly in the service might hide the actual problem, making debugging difficult. Always try to handle known exceptions first, then fall back on generic handling if necessary. This way, your @ControllerAdvice can consistently handle the custom exception and return a proper response to the client.
How much time to enough to learn spring boot from scratch? And what should I need to learn for 2 to 3 year experience person . Earlier worked on core java and SQL .please guide me
Don't use dark theme,
In intelij and postman,
Unable to see text.
Noted. Thanks for feedback
can you provide notes
Sure
Thanks you. I learn new topics from your video. But you don't provide source code -_-
I have updated project link in description
I dont know why all youtubers are promoting intellij ide Its not clearly visible..??
You mean not visible in video
Is it?