Skip to main content

How to handle exceptions in REST services (JAX-RS and SpringBoot)

Exception handling is vital aspect of any application or service. Exceptions should be handled properly and appropriate messages must be generated to end user or service in case of any exception. Same applies to REST services also whether they are used by some front-end application or some other service uses it to perform some operations.
It becomes tricky when we deal with REST services as we need to expose all the supported status codes for both success and error response which our service can generate, so client application or service can handle them appropriately.  Below are some samples of the status code.
200 - OK (API processes the request perfectly)
404 - Not found (Request URI or resource is not available)
500 - Internal server error (Request failed  due to some error at runtime at service side)

There are multiple ways to handle the exceptions which we will see in below sections.

Manual exception handling

We can handle the exception manually also like using try-catch combination but we need to do that at each service level. May be we will be ending up with lot of duplicate code for some common exceptions and fair chances to miss it also in some places

Exception handling in SpringBoot with JAX-RS Rest service

JAX-RS uses ExceptionMapper to convert the exception to response. An exception mapper class need to be created by implementing ExceptionMapper interface and override the "toResponse()" method. It also should be annotated with @Provider so JAX-RS can find it during provider scanning phase and when a particular exception is thrown at runtime, JAX-RS will convert it to HTTP response as per mapper to send it to the requester.

Mapper class implementation

@Provider
public class MyExceptionHandler implements ExceptionMapper<Throwable>{

    @Override
    public Response toResponse(Throwable arg0) {
        return Response.status(Response.Status.BAD_REQUEST).entity(arg0.getMessage())
                .build();
    }
}

JAX-RS integration with SpringBoot

To implement the JAX-RS services with Spring we need to register the Jersey resource configuration. below code is for achieving the same purpose with SpringBoot. In below code we have registered the package "com.example.rest" where we keeping all our jax-rs code like REST endpoint classes, Providers etc.
@Configuration
public class AppConfig{

    @Bean
    public ResourceConfig jaxrsResourceConfig(){
        return new ResourceConfig().packages("com.example.rest");
    }
}

Service class implementation

@Path("/jaxrs")
public class JaxDemoRestService {

    @GET
    @Produces(MediaType.APPLICATION_JSON)
    @Path("/hello/{name}")
    public String welcome(@PathParam("name") String name) {
        if("error".equalsIgnoreCase(name))
            throw new RuntimeException("\"error\" can't be used as a name.");
        return "Hello "+name;
    }
}
Now run the application and hit below URL in browser.
http://localhost:8080/jaxrs/hello/error
You will get the below response and status code.
Status Code: 400
Response: "error" can't be used as a name.

Exception handling in SpringBoot Rest service

It is very easy to implement the exception handling in Spring boot using @ControllerAdvice and @ExceptionHandler annotations. By default the handlers defined in @ControllerAdvice annotated class are applied globally but we can change it to point to some specific packages using "basePackages" attribute. We can define many handler methods to handle the different exceptions using @ExceptionHandler annotation.

Controller Advice

@ControllerAdvice
public class ErrorHandlerConfig {
    
    @ExceptionHandler({RuntimeException.class})
    public ResponseEntity<String> handleRunTimeException(RuntimeException e) {
        return new ResponseEntity<>(e.getMessage(), BAD_REQUEST);
    }
}

Service class

@RestController
@RequestMapping("/rest")
public class HelloService {
    
    @RequestMapping("/welcome/{name}")
    @GET
    @Produces(MediaType.APPLICATION_JSON)
    public String welcome(@PathVariable("name") String name) {
        if("error".equalsIgnoreCase(name))
            throw new RuntimeException("\"error\" can't be used as a name.");
        return "Welcome "+name;
    }
}

Now run the application and hit below URL in browser.
http://localhost:8080/rest/welcome/error
You will get the below response and status code.
Status Code: 400
Response: "error" can't be used as a name.

Comments

  1. Your style is so unique compared to other people I have read stuff from. Many thanks forposting when you have the opportunity, Guess I will just bookmark this site K7 Total Security

    ReplyDelete
  2. Such a Nice post. Thanks for Awesome tips Keep it up .
    Traktor Pro Crack
    windowsup.net

    ReplyDelete
  3. I am a professional web blogger so visit my website link is given below!To get more information
    Plugin Boutique Scaler v Crack/

    ReplyDelete

Post a Comment

Popular Posts

Setting up kerberos in Mac OS X

Kerberos in MAC OS X Kerberos authentication allows the computers in same domain network to authenticate certain services with prompting the user for credentials. MAC OS X comes with Heimdal Kerberos which is an alternate implementation of the kerberos and uses LDAP as identity management database. Here we are going to learn how to setup a kerberos on MAC OS X which we will configure latter in our application. Installing Kerberos In MAC we can use Homebrew for installing any software package. Homebrew makes it very easy to install the kerberos by just executing a simple command as given below. brew install krb5 Once installation is complete, we need to set the below export commands in user's profile which will make the kerberos utility commands and compiler available to execute from anywhere. Open user's bash profile: vi ~/.bash_profile Add below lines: export PATH=/usr/local/opt/krb5/bin:$PATH export PATH=/usr/local/opt/krb5/sbin:$PATH export LDFLAGS=&

SpringBoot - @ConditionalOnProperty example for conditional bean initialization

@ConditionalOnProperty annotation is used to check if specified property available in the environment or it matches some specific value so it can control the execution of some part of code like bean creation. It may be useful in many cases for example enable/disable service if specific property is available. Below are the attributes which can be used for property check. havingValue - Provide the value which need to check against specified property otherwise it will check that value should not be false. matchIfMissing - If true it will match the condition and execute the annotated code when property itself is not available in environment. name - Name of the property to be tested. If you want to test single property then you can directly put the property name as string like "property.name" and if you have multiple properties to test then you can put the names like {"prop.name1","prop.name2"} prefix - It can be use when you want to apply some prefix to

Multiple data source with Spring boot, batch and cloud task

Here we will see how we can configure different datasource for application and batch. By default, Spring batch stores the job details and execution details in database. If separate data source is not configured for spring batch then it will use the available data source in your application if configured and create batch related tables there. Which may be the unwanted burden on application database and we would like to configure separate database for spring batch. To overcome this situation we will configure the different datasource for spring batch using in-memory database, since we don't want to store batch job details permanently. Other thing is the configuration of  spring cloud task in case of multiple datasource and it must point to the same data source which is pointed by spring batch. In below sections, we will se how to configure application, batch and cloud task related data sources. Application Data Source Define the data source in application properties or yml con

Entity to DTO conversion in Java using Jackson

It's very common to have the DTO class for a given entity in any application. When persisting data, we use entity objects and when we need to provide the data to end user/application we use DTO class. Due to this we may need to have similar properties on DTO class as we have in our Entity class and to share the data we populate DTO objects using entity objects. To do this we may need to call getter on entity and then setter on DTO for the same data which increases number of code line. Also if number of DTOs are high then we need to write lot of code to just get and set the values or vice-versa. To overcome this problem we are going to use Jackson API and will see how to do it with minimal code only. Maven dependency <dependency> <groupId>com.fasterxml.jackson.core</groupId> <artifactId>jackson-databind</artifactId> <version>2.9.9</version> </dependency> Entity class Below is