What's the big advantage of using JTA over resource local transactions? On 21/12/2008, at 2:34 AM, Derek Chen-Becker wrote:
> Also, if you want lazy transactions it means you can't use JTA; as > far as I know, a JTA-aware EM wants the transaction to already exist > at the time that the EM is created. If that's not an issue and > you're using resource local transactions, transactions are pretty > inexpensive since they're essentially just turning off JDBC's > autocommit. I'll have a look at the JPA demo code to see if anything is changed. > On Sat, Dec 20, 2008 at 8:31 AM, Derek Chen-Becker <[email protected] > > wrote: > I would suggest looking at the JPA demo code in liftweb under the > sites directory. The JPA.scala and Model.scala have some code in > there for handling transactions. There's also a wrapEM method that > can help with catching and handling exceptions. I have a branch > underway that improves on the code a bit (wip-dcb-jpa-jta), but I'm > stuck at the moment because of a weird issue with Jetty JNDI. I may > end up just merging some of those changes back into trunk since it > looks like it may be a while before that's resolved. > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
