 Hello, welcome back. In the last video, we saw how to import code into code-ready workspaces, how to edit the code using the containerized editor, Eclipse Chain, and how to commit those changes, test them locally, push them back to the remote Git repository and all that. In this video, we will look at how to debug an application using that. But before we do that, let's update the project's configuration so that we can get a Maven view of it. Click on the project, update project's configuration, and here you see that it's, by default, blank. So let's select Java and Maven. Let's save it. Quickly, you will see the Java view of it. Now, in order to debug the application, we have to create a Maven command to be able to debug the app. I added a debug command in advance, and let's look at how this command is. In the last video, we saw how to add a new. This command is very similar to our build command that we used last time. We are providing the same Maven options. We are using Spring Boot Run, local profile, just like last time. The other arguments we are providing are the JVM arguments that you would supply to the Spring Boot application to enable debugging using these options. I'll be providing these options on a blog that will be posted along with this video. So look at the blog in order to copy paste these options. This is address 4005. You can choose any code number here. I chose 4005. We will be connecting to this port to debug the application. Now, let's go back to our code. In the database service, you'll see a food controller and get all in this food controller and set a break point on this line 60. So let's look at the debug view. We should see food controller.java line 60 as added as a break point. We'll just click on the number to add a break point. Since we added the debug command, we should see the debug command as part of the palette. So we'll select debug command and we'll run it. The debug process just started. It is building the app and it is listening for the DT socket at 4005. In order to connect to this application to debug, let's click on this run edit debug configurations. Under java, there should be a remote java. If it doesn't exist, you would want to create one. Call it remote java. You would want the host name as local host. Port number. In our case, we are going to connect to port 4005. So I created 4005. So if this one doesn't exist, you would want to create a new one by clicking on this plus button. In my case, since I already created it, I just press on the debug option here and it will try to connect to localhost at 4005. Now it says the remote debugger is connected. Now let's go back to the terminal window. Since the connection is made, it will take a minute for the app to completely come up. You should see the Tomcat has started and the bootstrap application has come up. So this is an indication to say that the app is up now. So let's start debugging. And in order to debug the app, let's access this URL. This will try to bring up the application, but the food list has not come because we have set up a break point in the food controller when the iterator fetches all the foods. So the control has stopped here. Again, let's switch to the debug mode by clicking on this button. And we can do step-by-step debugging by stepping into, stepping over, stepping out or running to the cursor. Step over. I will let it resume now. And let's go back to the application and see you see the complete foods list here. Again, let's try to add a new food. Save it. The save is complete, but the food list is not refreshed. And the reason it's waiting here again at our break point, let's resume it again. You see the complete foods list. So this is an example of how you can do step-by-step debugging using the Codery workspaces. I hope you enjoyed this video. Thanks a lot for watching.