Why Doesn't @Transactional Work When Calling a Method Within the Same Class in Spring?

Spring @Transaction Method Call Within the Same Class: Unexpected Behavior

In Spring, annotations like @Transaction allow developers to manage transactions effortlessly. However, a peculiar issue arises when attempting to call a transactional method (@Transactional) from within the same class it's defined in.

Specifically, a developer may encounter a situation where a caller method within the same class that holds a @Transactional method fails to trigger the expected transactional behavior. To address this issue, let's delve into the underlying reason.

CGLIB and AspectJ

Spring's default transaction handling mechanism employs CGLIB to dynamically generate and enhance Java classes to create proxies for Spring Beans. CGLIB, however, faces limitations when handling method invocations within the same class. As a result, when you invoke a @Transactional method from within the same class, CGLIB fails to intercept the transaction, leading to the absence of transactional behavior.

Aspect-Oriented Programming (AOP)

The solution to this issue lies in utilizing Aspect-Oriented Programming (AOP) to handle transactions. AOP allows us to intercept and modify program behavior without modifying the source code itself.

Configuration for AspectJ

To configure Spring to use AspectJ for transaction management, you must add the following configuration:

<tx:annotation-driven mode="aspectj"/>

If using Spring versions below 3.0, you must also add:

<bean class="org.springframework.transaction.aspectj.AnnotationTransactionAspect" factory-method="aspectOf">
    <property name="transactionManager" ref="transactionManager"/>
</bean>

Refactoring Code

Another viable solution, especially if AOP is not feasible, is to refactor your code. Instead of invoking the transactional method from within the same class, create a separate class that delegates the transaction handling to the transactional method. This approach ensures that Spring's default transaction handling mechanism functions correctly.

The above is the detailed content of Why Doesn't @Transactional Work When Calling a Method Within the Same Class in Spring?. For more information, please follow other related articles on the PHP Chinese website!