Transaction aspect order

[ziba]

I'm using Spring 2.0 declarative transactions with <tx:annotation-driven/> and want an interceptor to be called *before* commit.

The problem is that the "order" property of the transaction aspect is Integer.MAX_VALUE so I can't use a higher value in my aspect.

As a workaround I'm also using Integer.MAX_VALUE and it is actually being called before commit, but I'm worried if it is just by luck.

And what if I have more aspects that must be ordered before commit? Is it possible to change the order property of transaction aspect? The assumption that nothing will intercept after "begin transaction" and before "commit" is too restrictive...

[Andrei Stefan]

Doesn't <tx:annotation-driven/> have an 'order' attribute, also, to adjust the order aspects are applied ?

[ziba]

Unfortunately not...

[Andrei Stefan]

'order' attribute has been added starting with Spring version 2.0.3.
Take a look at this thread for more details.

[ziba]

Thanks! I didn't noticed it before, my IDE was lying to me...

My problem now is how to put the aspect order from a static field into an attribute! If only it was a property...

It seems that I will need to convert tx:annotation-driven into a explicit transaction configuration with advices, attributes, etc... Or there is another way?

[Marten Deinum]

Why? simply specify an order attribute on the annotation-driven tag. If you want it to be referenced from a static from inside a class use a ConstantsBean. Check the util:constant namespace for that.

<tx:annotation-driven order="1"/>