Spring's @Transactional annotation relies on AOP proxies, not magic, and is easy to misuse in ways that silently corrupt data. Key pitfalls include self-invocation (calling a @Transactional method from within the same class bypasses the proxy), checked exceptions not triggering rollbacks by default, and the hidden costs of
Sort: