Raise warning when Interception code fails [SPR-15308]

[spring-projects-issues]

Muhammad opened SPR-15308 and commented

Spring AOP Annotations (typically @Transactional) not working as expected when being called on a method from the same class or called on a non-public (using default spring/springboot configurations).

Most of the time developers (including me) forget about it (or even didn't expect such behaviour at all)

It would be so much gentle if spring log at some INFO+ level about the @Transactional annotation is there but without any affect cause to unsatisfied condition.

---

No further details from SPR-15308

[spring-projects-issues]

Juergen Hoeller commented

I'm afraid there is not much we can do here: An @Transactional method may get invoked from both externally and within the class, only having an effect in the former case (in proxy mode). For the within-class case, by definition, we cannot intercept the call... so we cannot log a specific warning here either. So on annotation introspection, we cannot cleanly differentiate between valid and invalid cases here... and on invocation, we don't get the chance to intercept the invalid cases to begin with.

[spring-projects-issues]

Muhammad commented

Clear now, Thanks for your time.