That's really odd. As far as I know the only thing JPA related that might have changed is for the JPA Demo site (pom Hibernate version change). The transaction handling code is all in ScalaJPA, which also hasn't changed. JndiEMF explicitly opens a transaction before it even retrieves the EM from JNDI, so I don't know how you could be getting that kind of error. If you could give me more details (on-list or privately) I'd like to figure out what's going on here.
Derek On Thu, Nov 12, 2009 at 5:49 PM, Kris Nuttycombe <kris.nuttyco...@gmail.com>wrote: > > Hi, all (Derek! :), > > Have there been significant changes in how transactions are handled by > lift-jpa since M6? Due to the rearrangement of the repository, I'm > having a hard time figuring out if the code has changed. > > I have a repeatable issue that shows up when changing between M6 and > SNAPSHOT wherein I now get > javax.persistence.TransactionRequiredExceptions when doing a merge > using a JndiEMF with RequestVarEM in an AJAX callback. > > Has anything major changed in this timeframe? > > Kris > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
