If you define your database pools at the server level in resin.conf,
then you need to put the JDBC drivers in the resin/lib directory so the
pools can be created when the server starts.
Privileged/Confidential Information may be contained in this message. If you
are not the addressee indicated in
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
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
