Why Doesn't @Transactional Work on Private Spring Bean Methods?

Spring @Transactional Annotation on Private Methods

If a @Transactional annotation is applied to a private method in a Spring bean, it will not have any effect. This is because the proxy generator, which is responsible for creating proxies for Spring beans, ignores private methods when generating the proxy.

For example, consider the following Spring bean:

public class Bean {
    public void doStuff() {
        doPrivateStuff();
    }

    @Transactional
    private void doPrivateStuff() {

    }
}

When the application context is created, a proxy will be created for the Bean class. However, the @Transactional annotation on the doPrivateStuff method will be ignored, and the method will not exhibit the configured transactional settings.

This behavior is documented in Spring Manual chapter 10.5.6:

When using proxies, you should apply the @Transactional annotation only to methods with public visibility. If you do annotate protected, private or package-visible methods with the @Transactional annotation, no error is raised, but the annotated method does not exhibit the configured transactional settings. Consider the use of AspectJ (see below) if you need to annotate non-public methods.

The above is the detailed content of Why Doesn't @Transactional Work on Private Spring Bean Methods?. For more information, please follow other related articles on the PHP Chinese website!