Implementing Exception Handling- 404 Resource Not Found

by Online Tutorials Library July 14, 2022

Implementing Exception Handling- 404 Resource Not Found

In the previous section, we had returned the proper response status of CREATED when we created the resource. In this section, we will discuss what should be the response when a user resource does not exist.

Let’s try and execute a simple response.

Step 1: Open Rest client Postman and select the Get method.

Step 2: Click on the History tab and choose the Get request.

Step 3: Type the URI http://localhost:8080/users/{id}. The user id should not exist.

Step 4: Click on the Send Button.

We get the Status: 200 OK and empty body which is a successful response even though the resource does not exist. But it is not the proper response when a resource does not exist.

Let’s fix that first.

Step 1: Open the UserResource.java file.

Step 2: Create a UserNotFoundException. It is a checked exception.

  @GetMapping(“/users/{id}”)  public User retriveUser(@PathVariable int id)  {  User user= service.findOne(id);  if(user==null)  //runtime exception  throw new UserNotFoundException(“id: “+ id);  return user;  }  

Step 3: Create UserNotFoundException class.

Step 4: Generate Constructors from Superclass.

Right-click on the file -> Source -> Generate Constructors from Superclass… -> check the RuntimeException(String) -> Generate.

UserNotFoundException.java

  package com.tutoraspire.server.main.user;  public class UserNotFoundException extends RuntimeException   {  public UserNotFoundException(String message)   {  super(message);  }  }  

Step 5: Open the Rest Client Postman and generate a Get response as we have done before. It shows the Status: 500 Internal Server Error.

But the Status: 500 Internal Server Error is not the appropriate response for the resource not found. So, we will add an annotation @ResponseStatus to generate the Status: 404 Not Found.

UserNotFoundException.java

  package com.tutoraspire.server.main.user;  import org.springframework.http.HttpStatus;  import org.springframework.web.bind.annotation.ResponseStatus;  @ResponseStatus(HttpStatus.NOT_FOUND)  public class UserNotFoundException extends RuntimeException   {  public UserNotFoundException(String message)   {  super(message);  }  }  

Step 6: Again move to Postman and generate a Get request.

We get the proper response Status: 404 Not Found when a user resource does not exist. The body of the request provided by default error handling that’s why we are getting this return status back.

The combination of Spring Boot and Spring Web MVC framework provides error handling. Spring Boot auto-configures some default exception handling. It is important to have a consistent exception message which is obtained for all the services inside our enterprise.

If we have a big organization and each of the services returns the exception messages in a different way, so it is not good. It would be good if we define a standard exception structure which is followed by across all the RESTful Services.

Click here to download Not Found project

Click here to download 500 Internal Server Error project

Next TopicImplementing Generic Exception Handling for all Resources

Implementing Exception Handling- 404 Resource Not Found

Implementing Exception Handling- 404 Resource Not Found

Difference between Method Overloading and Method Overriding in java

First JavaFX Application

You may also like