Sometimes we need to handle checked exceptions from an external API and it enforces you to use try-catch Block, i think the appropiate way in this case is retrow the exception. I also agree with the approach of handle exceptions with proper status code.
yeah, In checked exceptions you don't need to catch exception also, just throws exception to the spring boot, then handle it from advice and return according status code to the client
Most likely handled by a exception handler class, you will intercept most common exceptions there and only rethrow if you need a specific or custom exception
thank you, your video teaches me using intellij and luckily, the shortcuts are same than pycharm, it is better slowly learning intellij for me than looking at the pdf and i don't forget easily this way
Hi Nelson, Thank you🤝 for the wonderful lessons. I am a java developer, currently i have been working on one project where I have to process/validate against 50-60 rules, each rule is created as a class due it's complexity. Now these many classes I have to inject into the service class for the processing... In the service class I am using the switch case to process the desired rule. Could you please suggest any solid dependency injection pattern or another way here. Thank you in advance!
the try and catch was made for the .save method except that method could also throw its exception if it faced error while logging in the database so really there was no need for the try and catch unless the catch had something useful to do which didn't in this case but also sometimes the the handler (try-catch block) is made by force because the .save method can throw an exception therefore the API enforces the rule on you
The amount of code I've looked at that doesn't swallows exceptions and doesn't use status code or uses it poorly since I started working on the industry is astonishing (and I've been working for 5 months only lol). But not so surprising when I've had to work with APIs that use GET requests to put/post/patch data
Yep, same here When I have some time, I just do refactoring work and then create a new branch with the refactored code ready to be merged with the main branch (of course I write tests before changing anything complex)
In a case where the code is unable to save to the DB say a network connection issue or DB is out or down won’t the try catch come in handy. Or does he/she check at every instance if the DB connection is up/accessible before saving into it.
Thanks man. I hope the we all learn something here which we have in Sha Allah. And please Nelson, can you make a video on multiple implementation of UserDetaisService and a custom authentication provider so that one can authenticate users from different tables. I think that will help a lot, because I'm struggling to do that for about 3 to 4 days now, I did some research and the only thing I found was I have to use WebSecurityConfigurerAdapter which is now deprecated. It'll be a big help if you'll do that for use, especially me. JazaakAllahu khairan. May Allah increase you in knowledge and wisdom. Assalamualaikum
He means to say that do not send status code 200 if any exception is occurred. Handle and throw an appropriate status code and message here or use controlleradvice for the same
I will admit that I do this when creating microservices. Generally, I record a request to the appropriate request table and if and when it fails, I curate a response code and message that details exactly where the action failed. I prefer to curate detailed response code and message rather than just error 500 that show just that an internal exception occurred.
At least he was logging something. I saw code where the developer just added a comment in the catch block like // ignore. Most likely he thought that this error will never happen but unfortunately it did and it took me quite some time to find that place and finally be able to debug it and fix the problem. It was some parsing shenanigans with date and number and obviously the format changed at some point which made his code no longer work 😅
What's wrong with the code, I wasn't able to find it. Why does this give the error in case of status 200. The catch block will only execute in case it finds any Exception then why this is wrong. (can someone explain to me)
The server will send 200 OK to the client, regardless the request is fail or successfull. Since the catch only log the error. Moreover, it will save null data to the database.
I'm not familiar with java. But shouldn't employeeRepository.save(employee) be checked for insertion error? Does the JPA automatically throws an error?
Actually Jpa doesn't automatically throw errors. But then you have the option to handle errors in your service class as well as use some quite useful annotations for input validation. All of these ensure you won't have an error while saving an object
why did you remove my course from the website which I paid for. and now since you increased the price of that course you are offering me only $15 refund. This is not acceptable.
hi, For my case i send as response an Object named ReturnObject = {"codeException": , "messageException": , "data"} with code 200. if there is no exception the "data" attribute contains the Result Object . if there's an excetion i send codeException and messageException. So allways i have ResponseStatus = 200. And in FRONT i manage the response in Interceptor. If i do this , it's considered as a swallow exceptions?