Another note is that ScalaJPA provides a pretty thin wrapper on a JPA persistence unit. Each persistence unit represents *one* database, so you actually need more than one persistence unit to have connections to two databases. I recently added support in 1.2-SNAPSHOT so that you can provide a property map to LocalEMF to allow you to use the same unit with different database connections, but if you're using JNDI that won't work. If you're still having the issue, could you post some code that shows where it's failing?
Thanks, Derek On Tue, Oct 20, 2009 at 6:37 AM, Jean-Luc <jlcane...@gmail.com> wrote: > Which liftweb version are you using ? > I've signaled a bug a few month ago, it was very very quickly fixed (thank > you again Derek for your reactivity !). My jpa apps are in production and I > have no such issue remaining, scalajpa looks like to be very stable. > > Once, I wrongly specified a wrong "persistence-unit/@name" value in test > mode, and it caused the same symptoms. Have you verified that your LocalEMF > configuration suits your META-INF/persistence.xml file ? > > Maybe you want to copy / paste your source code for a quick review ? > > > Jean-Luc > > 2009/10/19 TSP <tim.pig...@optrak.co.uk> > >> >> I'm using scalajpa and have just downloaded source from github >> My application has 2 databases and my unit tests are creating tables >> for the second database in the first. >> This was a reported issue back around June I think, but the posts seem >> to imply it was fixed. >> Was it not? >> Thanks >> Tim >> >> > > > -- > Jean-Luc Canela > jlcane...@gmail.com > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
