You have to get a driver for the database you are using.  You have to get a
whole mydatabase.jar of files from them, implementing the jdbc interfaces.
Then you put those into /lib/ext/ in Tomcat and  j2ee and /jre/lib/ext/ in
j2se.  These do not need to be specified in CLASSPATH.

-----Original Message-----
From: Mark <[EMAIL PROTECTED]>
To: Tomcat Users List <[EMAIL PROTECTED]>
Date: Thursday, November 29, 2001 2:20 PM
Subject: Re: OKAY: HERE GOES. THIS IS GETTING INTERESTING. Re: Tomcat
4.0/JDBC driver configuration?


>To answer your question, yes I understand what a servlet's init() method is
>and when it's called.   You've provided valuable information and I
>basically understand it, providing jdbc setup info through init-params in
>web.xml.  I'll definitely plan on looking closer at javax.jdbc - I've only
>used the (as you put it) 'kiddy' jdbc stuff in the past.
>
>However, my question is about the physical location of the jdbc driver .jar
>file.  In other environments I've worked with, including the location of
>the .jar in the CLASSPATH was sufficient.  With Tomcat, does one have to
>copy the driver to ../common/lib?  If so, that doesn't seem like a very
>good situation to be in especially in a production environment.  I tried to
>modify CLASSPATH in the startup scripts to see if that'd work, but
>everything went haywire after that under Win2k - *nothing* worked even
>after backing out the simple change (even had to reboot to get things in
>working order again).
>
>I suspect I'm again missing/not understanding something.
>
>Thanks again for your help...
>Mark
>


--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>

Reply via email to