Spring Boot @Transactional No rollback workaround

When a compile-time exception is thrown, the transaction does not roll back, and the employee successfully inserts the data.

1 @Transactional2      PublicEmployee Saveemployee ()throwsException {3Employee Employee =NewEmployee ();4Employee.setname ("ZZ");5Employee.setage (60);6 Employeemapper.insert (employee);7         8         if(Employee.getage () = = 60) {9             Throw NewException ("Age = 60");Ten         } One  ASalary Salary =NewSalary (); -Salary.setsalary (60); - Salarymapper.insert (salary); the  -         returnemployee; -}

Reason:

The default spring transaction is rolled back only when an uncaught runtimeexception occurs.

Spring AOP Exception Trapping principle: The method being intercepted explicitly throws an exception and cannot be processed so that the AOP agent catches the exception of the method before it can be rolled back, and AOP catches only runtimeexception exceptions by default. However, a specific exception can be captured and rolled back by configuration

In other words, no try catch is used in the service's method or a throw new Runtimeexcetpion () is finally added to the catch, so that the program can be caught by AOP and then rolled back.

-----------------------------------------------------------------------------------------

Solution:
Scenario 1. For example, the service layer processes the transaction, then no exception is caught in the methods in the service, or the throw new RuntimeException () statement is finally added to the catch statement so that AOP catches the exception and then rolls back.

Scenario 2. Add: Transactionaspectsupport.currenttransactionstatus (). Setrollbackonly () in the catch statement of the service layer method; statement, manual rollback, This way the upper layer does not have to deal with exceptions.

Via

Http://www.cnblogs.com/leohe/p/6673096.html

Spring Boot @Transactional No rollback workaround