add the possibility to specify the order when using <tx:annotation-driven> [SPR-2501]

[spring-projects-issues]

Tareq Abedrabbo opened SPR-2501 and commented

tx:annotation-driven now does not allow to specify an order for the transaction interceptor ; it has the default lowest order making it impossible to run before other aspects.
It would be useful to allow specifing order at tx:annotation-driven level or maybe at the annotaion (@Transactional) level.

---

Affects: 2.0 final

Issue Links:

• Document the 'order' attribute of the <tx:annotation-driven> element. [SPR-3061] #7747 Document the 'order' attribute of the tx:annotation-driven element. ("is depended on by")

6 votes, 7 watchers

[spring-projects-issues]

Jason Bennett commented

This fix is required to be able to do AOP work inside of a transaction. We have auditing code that would be perfect to move into an aspect, but it must be done after the facade completes and before the transaction is done.

While I could use tx-advise, being able to stay with annotations would be best.

[spring-projects-issues]

Juergen Hoeller commented

I've finally added an "order" attribute to the "tx:annotation-driven" tag, determining the order of the tx advisor in the advice chain.

Sorry for not addressing this earlier, BTW; this issue somehow slipped through.

Juergen