Did you really count 😀

Thanks bro 👍🏻🙏

Sure

Sure

👍🏻

Noted. Thanks for feedback

Sure I will

Thanks 🙏

Thanks bro, Sure

Sure

Intellij

Sure

Happy to help

Yes

Yes. I am adding one video each week

Sure Ill update the link in description soon

Sure

Thanks 🙏

I already have few videos on that. checkout my java playlist

I have re uploaded video pls check

Thanks

Glad it helped

Have re uploaded. Pls check

Thank you so much 😀

sure, share your mail id, ill email you

Haha Right 😅

Thanks 🙏

Yes you can

Sure i will try to 😅

Hi Bipin REST APIs are indeed stateless, meaning each request from a client to a server must contain all the information needed to understand and process the request. The server does not store any state about the client session between requests. However, session maintenance is typically handled by using mechanisms such as: Tokens (JWT or OAuth): The server issues a token upon successful authentication. This token is then sent by the client with every request (usually in the headers), allowing the server to authenticate and authorize the client without needing to track session state. Cookies: While REST is stateless, cookies (issued by the server) are a way for clients to store session data on the client-side and send it back to the server with each request. URL Parameters: Some APIs pass session information through URL parameters, though this method is less common for security reasons. These approaches allow REST APIs to maintain user sessions without violating the stateless constraint.

Uploaded new video

Sure

Sure. Will share it

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

Thanks 🙏

Thanks 🙏

Pls share email