In a Spring Boot application, a @Transactional method is called from another method within the same bean (self-invocation). Even with CGLIB proxying enabled, the transaction is not applied. How does Spring’s proxy-based AOP implementation cause this behavior internally, and what design choices in the framework prevent transaction interception in this case?

SRIDHARSHINI S's user avatar

New contributor

SRIDHARSHINI S is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.