Hello Jaie, I'm posting about a year later on this thread, but we are using Play + Guice + jOOQ (which has been awesome so far), and having some issues with our transactions setup. I was wondering what you think of the following?
- Initially, we defined a Guice interceptor to handle transactions for our service methods and our controllers. But we found that getting the Guice interceptor to catch exceptions thrown by the controller instance was difficult. - So we simplified and said "let's wrap every controller call in a transaction", and since we're going to be using Akka for some background processing, when Akka makes any database calls, we'll say "let's wrap every Actor send/receive in a transaction, too. The obvious benefit of all of this is simplicity, but I'm wondering if there are performance implications for making everything a transaction (initial Googling indicated no, but still researching). I also saw in a separate post that you're using Spring transactions. But what is really the benefit of all the muscle of Spring Transactions over just plain old boring controller and Akka wrappers? Thanks for your input! On Sunday, July 28, 2013 12:56:33 AM UTC-7, Lukas Eder wrote: > > Dear group, > > I would like to advertise a third-party piece of work by Jaie Wilson, who > has been creating a Play Framework integration for jOOQ: > https://github.com/jaiew/play-jooq > > This integration was discussed here in this issue: > https://github.com/jOOQ/jOOQ/issues/768 > > Feel free to join the discussion and provide feedback if you're using / > planning to use jOOQ with Play Framework > > Best Regards, > Lukas > -- 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.
