Spring Core · interview question
How would you explain a potential consequence of self-invocation in a Spring bean with @Transactional methods in an interview?
Multiple choiceHardchapter-9-curatedpremiumspring-corecontrollers-services-repositories
Answer and explanation
Correct answer
C. Transaction not applied
Why
When a method within a Spring bean calls another @Transactional method in the same class, the transaction is not applied because the call bypasses the proxy that handles the transaction management.
Test yourself on Spring Core
A free test with instant, explained results. No account needed.
More Spring Core questions
- In a Spring Boot application, what happens if a method annotated with @Transactional calls a private method also…
- Which layer should coordinate inventory checks, payment, and order persistence for a checkout request?
- What role do Entities typically play in a Spring Boot application?
- How can you externalize configuration in a Spring Boot application?
- Which issue might arise from using field injection in Spring Boot, particularly when managing dependencies?
- In a Spring Boot application, what is the main purpose of the @ComponentScan annotation?