I had the same problem a while ago. I'm not sure if I fixed it then, but I think it had to do with the db still being open possibly. When the code changes does the servlet get undeployed? You might need to run derby in server mode. Lately I've been launching jetty without maven, and to get it to reload eclipse calls an ant script that touches the context.xml. I'm using h2 in tcp mode. Another option is JavaRebel which often obviates the need to redeploy. Sorry I can't help you better--I'm interested in any more information there is about this too.
------------------------------------- David Pollak<feeder.of.the.be...@gmail.com> wrote: I won't have a chance to look at it until next week, but maybe somebody else could step in here and help. On Wed, Jun 24, 2009 at 7:16 AM, Nolan Darilek <no...@thewordnerd.info>wrote: > > On 06/24/2009 08:54 AM, David Pollak wrote: > > Are you using JNDI or your own connection manager to connect to the > RDBMS? > > > I'm new to this, but I'm guessing the latter. In any case, I haven't > touched whatever values the snapshot sets up in Boot.scala, nor have I > set any properties, so it's stock Derby. > > > > -- Lift, the simply functional web framework http://liftweb.net Beginning Scala http://www.apress.com/book/view/1430219890 Follow me: http://twitter.com/dpp Git some: http://github.com/dpp --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
