if your driver is a pure java driver(type 4, I think) then you would be ok. If your driver uses native libraries for its java implementation, then you will have a problem.
you want to put the jar in your /common/lib so that it is is loaded once and shared for all contexts that need it. This way a reload will not affect it. Charlie > -----Original Message----- > From: Chris Brown [mailto:[EMAIL PROTECTED]] > Sent: Monday, September 23, 2002 3:57 AM > To: tomcat-user > Subject: Classloaders, JDBC drivers (etc.), and reloading webapps with > the /manager > > > > Hello, > > If I include a JAR file for a JDBC driver within my webapp's > /WEB-INF/lib > path, calling Class.forName("some.driver") registers the > driver with the > java.sql DriverManager. No problem... until I reload the > context using the > /manager webapp. > > Is the class definition (and in particular, the driver instance) still > valid, given that the classloader used for the driver (and all classes > loaded by it, including the driver) will have been reloaded ? > > Thanks, > Chris B. > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
