I got the idea from being really dumb. I was just about to post as much. I had a typo in my resin.xml file, and it wasn't finding my webapp, so of course it couldn't find the driver.
It's working just fine. I think, a long time ago, it was more problematic, and I might've had that thought stuck in my head. On Jun 24, 2009, at 18:14:30, Joseph Dane wrote: > where'd you get that idea? unless things have changed very > dramatically since 3.1.6 (the version I'm using) you can put database > drivers in WEB-INF/lib just fine. > > I don't know a simple way to find out the location from which classes > are loaded. I agree -- that could be quite useful. > > If you're having problem with the driver living in WEB-INF/lib, then > it's probably because you've got something *else* in resin/lib that > needs the driver. the classloaders can look "up", but they can't look > "down". > > > On Jun 24, 2009, at 3:05 PM, Rick Mann wrote: > >> It seems to me that resin ought to be able to find the MySQL JDBC >> driver when the jar is loaded from WEB-INF/lib, rather than requiring >> it to be installed in resin's lib. >> >> Is there a way to see when each specific jar gets loaded, so I can >> sort of verify that resin should have access to it or not? >> >> Thanks. >> >> >> >> _______________________________________________ >> resin-interest mailing list >> resin-interest@caucho.com >> http://maillist.caucho.com/mailman/listinfo/resin-interest > > -- > > joe > > > > _______________________________________________ > resin-interest mailing list > resin-interest@caucho.com > http://maillist.caucho.com/mailman/listinfo/resin-interest _______________________________________________ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
