DEV Community πŸ‘©β€πŸ’»πŸ‘¨β€πŸ’»

DEV Community πŸ‘©β€πŸ’»πŸ‘¨β€πŸ’» is a community of 963,673 amazing developers

We're a place where coders share, stay up-to-date and grow their careers.

Create account Log in
irshad sheikh
irshad sheikh

Posted on • Originally published at initgrep.com on

@Transactional Rollback options in Spring Data

Transactions manage the changes that are performed in a system. The main purpose of transactions is to provide ACID characteristics to guarantee data validity.

Spring provides a consistent programming model for transactions. @EnableTransactionManagement is used to enable transaction management for the spring application. Spring boot enables it by default.

@Transactional annotation is used to designate the transaction boundary.

  • If this annotation is provided on the class then all the methods of the class have transactions enabled.
  • If no annotation is provided on the class, then the individual methods will require the explicit @Transactional annotation - if required.

@Transactional annotation provides various options to control the behavior of the transaction. We will only focus on two options that help in defining the rollback behavior of the transaction.

The default behavior of the transactions is to rollback for the runtime exceptions and the errors. You wouldn’t need to change the defaults in most of the scenarios. However, there are some cases, where you might care about whether the transaction should rollback or not.

Let’s consider the below example β€”


class ProductService{

    @Transactional
    public void processProducts(){

            saveAllProducts(...products); // saves the data in the database
            sendNotification();
    }

    /*
    * sendNotification throws an exception
    */
    private void sendNotification() throws NotificationException{
        //sending the notification
    }

}

Enter fullscreen mode Exit fullscreen mode
  • processProducts() method supports the transaction.
  • saveAllProducts() saves the product data in the database.
  • sendNotification() sends the notification through some external system. It throws NotificationException for any failure.

This code will work just fine. The products will be saved and after that, the notifications will be sent.

However, if the external system is down and we are unable to send the notifications, NotificationException will happen and the transaction will rollback all the changes. This means, due to the notification failure, we are unable to save the products in the database.

Now, if we want to save the data irrespective of the notification operation success or failure. We would need to modify the default transaction rollback behavior.

@Transactional annotation provides two options dontRollbackOn and rollbackOn for the same.

You can check the complete post at here

Top comments (0)

Take a look at this:

Settings

Go to your customization settings to nudge your home feed to show content more relevant to your developer experience level. πŸ›