Hi Denis, I'm sorry for the delay.
2016-06-17 10:27 GMT+02:00 Denis Miorandi <[email protected]>: > I wouldn't call it "Mix" it's more a delegation process. Spring intercept > @Transactional annotation and delegate jooq to manage it, but actually I > don't know how jooq > can manage "start a new transaction" instead of "use current one" in some > cases. > The jOOQ model puts that responsibility into the Configuration.transactionProvider(), and implicitly also into Configuration.connectionProvider(). There is always a "current" Configuration, so the transaction semantics is clear. > Code is almost identical to the reference one into > > https://github.com/jOOQ/jOOQ/tree/master/jOOQ-examples/jOOQ-spring-boot-example > > The hot part is the following where is not possible do manage different > propagation style cause this parameter is not in ctx. > Of course I can implement provider as needed but *I don't know how to > have @Transactional parameters as input here*, to create transaction in > right way. > Unfortunately, I don't know it either. Would be interesting as a Stack Overflow question, I suspect. "How to get the current thread's context's @Transactional parameters via Spring APIs?" -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
