JPA requires that a transaction be in place before *any* persistence operations occur. The ScalaJPA stuff is supposed to handle it for you, so that's why I was wondering about stack traces. In particular, the RequestVarEM trait should start a new transaction when the request begins and close the transaction on exit.
Derek On Wed, May 13, 2009 at 2:14 PM, ngug <naftoli...@gmail.com> wrote: > > Thanks for looking. The stack traces aren't very helpful because they > concern the state which is caused by the previous sequence of events. > Anyway, why is there a transaction taking place in the first place? > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
