KITFORMA · EDITORIAL GUIDE
Why is @Transactional ignored by a same-bean method call?
KitForma editorial guide. In normal proxy-based transaction advice, a direct call through `this` does not re-enter the Spring proxy. An annotation can therefore exist while the expected boundary is absent.
Step-by-step guidance
In normal proxy-based transaction advice, a direct call through
this does not re-enter the Spring proxy. An annotation can therefore exist while the expected boundary is absent.
Move the transaction into a separate injected service with a clear public boundary, or use a transaction template when it better describes the operation. Call the injected bean instead of constructing it with new. Avoid self-injection solely to conceal confused service responsibilities.
Verify with a deliberate failure after a database write and inspect committed state. Alternative weaving configurations have different interception rules; this explanation applies to proxy-based advice, not every possible Spring configuration.Sources and verification
Sources checked:
Scope: This editorial guide is based on the cited sources and tool behavior. A forum question or a query observed for our site does not establish market search volume, low competition, guaranteed rankings or inadequate answers elsewhere.
This starter guide was prepared by KitForma with AI assistance. It is not presented as a real member question or an independent user review. Check the sources and the result with your own file; report corrections in the discussion.