Panagiotis Konstantinidis typed the following on 12:26 30/11/2000 +0000
> Now, I am using Apache v1.3.12 and Tomcat v3.1 (for Windows).
The first thing I would recommend is upgrading to Apache 1.3.14 and Tomcat 3.2,
since these are the latest stable versions. Tomcat in particular has fixed
a lot of
bugs since the version you're using.
>The thing is that everytime the line Class.for("org.gjt.mm.myswl.Driver");
>is encountered, Tomcat goes off (and I get the error message "Internal
>Server Error.
Do you mean Class.forName("org.gjt.mm.myswl.Driver")?
Have you checked your logs? You should get more accurate information about
what's going wrong from the stdout and stderr messages that Tomcat puts out:
these may be going to your console window, or they may be going to log files
in Tomcat's log directory.
Without more specific error information, I would make a guess that it has to
do with the classpath. Your JDBC driver must be in the classpath that the
Tomcat server is using, if not Class.forName() will throw an exception, which
would cause the behavior you're seeing. Try putting the JDBC driver .jar file
in the WEB-INF/lib directory.
Kief
---
bitBull makes the Internet bite: http://www.bitBull.com/demos/
