On Mon, 9 Jul 2001, Kevin HaleBoyes wrote:
Herein lies your problem. The classes12.jar(it has to be a jar not
a zip), has to be in TOMCAT_HOME/lib, not your webapps lib folder.
Think of it this way. Where do you configure the JDBCRealm? In
TOMCAT_HOME/conf/server.xml. The
I've been running Tomcat 4.0b5 since it was released and had the JDBCRealm
stuff working just fine. I've been using Oracle 8.1.7 (8i) on Linux RedHat
6.2. I upgraded just recently to RedHat 7.1 and Oracle 9i (9.0.1) and tried
to get my application working again but it is failing on the
The only change I made for 9i was to change the driverName from
oracle.jdbc.driver.OracleDriver to oracle.jdbc.OracleDriver
as recommended
by Oracle. In my application lib directory I made a link to
the classes12.zip
(and .jar file) and rebuilt. I've confirmed that the
[EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, July 09, 2001 10:34 AM
Subject: RE: (application library) ClassNotFoundException
The only change I made for 9i was to change the driverName from
oracle.jdbc.driver.OracleDriver to oracle.jdbc.OracleDriver
as recommended
by Oracle. In my
Herein lies your problem. The classes12.jar(it has to be a jar not
a zip), has to be in TOMCAT_HOME/lib, not your webapps lib folder.
Think of it this way. Where do you configure the JDBCRealm? In
TOMCAT_HOME/conf/server.xml. The server.xml file is parsed at
startup
and therefore the
So, this leads me to a follow up question. I know that I've
got the jar
file in the server/lib directory, is there any way to use that from my
application. If not then I have to have the exact same jar file in my
WEB-INF/lib directory to use Oracle JDBC in my application.
You could
From: Michael Wentzel
So, this leads me to a follow up question. I know that I've
got the jar
file in the server/lib directory, is there any way to use that
from my
application. If not then I have to have the exact same jar
file in my
WEB-INF/lib directory to use Oracle JDBC in my
You could always alter you startup script to so that the TOMCAT
CLASSPATH
contains the fully qualified oracle jar.
Ok that works, but is that the right thing to do?
K.
No, not really, but if you don't want to have multiple file copies
(which shouldn't be that much of a problem really)
