I have a method which is annotated with @Transactional and another custom annotation @Custom. This custom annotation is wrapped around an advice. The sequence of operation is like below:
1.Transactional method gets called
2.Sees @Transactional and @Custom
3.As @Custom is intercepted by around advice, it first executes code before invocation of method
4.invocationContext.proceed()
5.Transaction gets created
6.Actual method runs
7.Back to around advice and executes code after method invocation
I want to create the transaction before the advice is called. Like below:
1.Transactional method gets called
2.Sees @Transactional and @Custom
3.Transaction gets created (propagate this transaction to @Custom)
4.As @Custom is intercepted by around advice, it first executes code before invocation of method
5.invocationContext.proceed()
6.Actual method runs
7.Back to around advice and executes code after method invocation
So that both advice and method are in same transaction
Can we use @Order on @Transactional, so taht first my transacion is created and then the advice executed?
You could try adding @transaction(propagation=required)on top of @custom annotation . It may hopefully work
I guess
@EnableTransactionManagement(order = Ordered.HIGHEST_PRECEDENCE)
is the global config.If you want
@Transactional
just on this methodA()
, not for other methods, maybe you can define methodB()
to callA()
. This way will point out the order of annotations.Like this:
Yes, in the
@Configuration
class use:or whatever order you need