Amrinder,

I did change the class name to a known-to-be-invalid-name - "bugger" and NO
exceptions where thrown.  Which is what started me thinking that it was a path
issue.

The MyNullDriver scenario seems the same as what I am trying to do.  Other that
it being a made up driver name, what is different?

Dave


"Amrinder, Arora (Meritage)" wrote:

> I see.
>
> If I remember correctly, you had tried changing the class name to "bugger".
> In that case, did you catch any error while loading the class?  Also, can
> you put a test class, say MyNullDriver in the same directory as the driver,
> and put this line after your try catch clause
>
> $packagepath.MyNullDriver mnd = new $packagepath.MyNulldriver();
> System.out.println (mnd); //Using the same value of the package path
>
> --amrinder
>
> -----Original Message-----
> From: David Bustin [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, October 30, 2001 4:47 PM
> To: [EMAIL PROTECTED]
> Subject: Re: A Servlet using JDBC error
>
> Amrinder,
>
> answer 1) The DB driver is part of the zip file.  The zip file I have is an
> uncompressed archive.  I have also put this same file in the "path" as a
> *.jar
> file and I have also unziped and placed the classes directly into the
> "path".
>
> answer 2) I get NO exceptions caught in the catch clause.
>
> This definitely seems like it is a path issue.  The big question that is
> still
> -- what _is_ the "correct path?"  Do the *.jar/classes need to be in more
> that
> one location as they do if you are using JSP with Beans.  Will Tomcat search
> for
> class/jar files in any location that is NOT in the CLASSPATH?
>
> Dave
>
> "Amrinder, Arora (Meritage)" wrote:
>
> > Dave,
> >
> > You might have already checked this, but:
> >  Is the DB driver class that you are trying to use a part of the zip file?
> > [You can use WinZip to see the contents of the zip file to see if it
> indeed
> > contains the class file in directory structure that corresponds to the
> > package qualified name that you are using].
> >
> > secondly do you get any errors in the catch clause of
> > try {
> >     Class.forName ("_drive_class");
> > }
> >
> > \amrinder
> >
> > -----Original Message-----
> > From: David Bustin [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, October 30, 2001 3:32 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: A Servlet using JDBC error
> >
> > > Guru,
> > >
> > > Thank you for your time. To try to get past things you don't care about
> > and get
> > > to the things yo do care about.
> > >
> > > Here is a quick recap:
> > > I am using Tomcat 3.2 on NT 4.0 connecting to Oracle 8.1.6 on a UNIX
> host.
> > I
> > > am also running directly on the same NT 4.0 that is running Tomcat,
> > therefore
> > > only the Oracle database is remote across the network.
> > >
> > > My current ClassPath:
> > >
> >
> .;g:\java;C:\jdk1.3.1\jre\lib\;C:\jdk1.3.1\jre\lib\rt.jar;C:\dggui\jakarta-t
> > omcat-3.2.3\lib;
> > >
> > >
> >
> C:\dggui\jakarta-tomcat-3.2.3\lib\servlet.jar;C:\dggui\jakarta-tomcat-3.2.3\
> > lib\jasper.jar;
> > >
> > > C:\Orant\JDBC\classes12.zip;
> > >
> > > My steps:
> > > 1) made sure Tomcat was shutdown.
> > > 2) I loaded the test app (DBservlet.java & DBservlet.class) into:
> > > C:\install_dir\jakarta-tomcat-3.2.3\webapps\examples\WEB-INF\classes
> > > 3) restarted Tomcat.
> > > 4) accessed my app.
> > > 5) received errors....
> > >
> > > I added the classes12.zip to my CLASSPATH before I tried to compile the
> > first
> > > time but the results are always the same.  I was wondering if it had
> > anything
> > > to do with connecting to the database on a UNIX server from NT 4.0
> running
> > > Tomcat 3.2.  So I tried to switch to the oci driver.  I now get more
> > errors
> > > that suggest that the classpath is not setup correctly.
> > >
> > > Where should the classes12.zip and/or classes12.jar be located?
> > >
> > > TIA,
> > > Dave
> > >
> > > "Raghupathy, Gurumoorthy" wrote:
> > >
> > > > yes please add it...
> > > > both are diffrent...
> > > > which server ( servlet engine do you use )
> > > >
> > > > reagrds
> > > > guru
> >
> >
> ___________________________________________________________________________
> > To unsubscribe, send email to [EMAIL PROTECTED] and include in the
> body
> > of the message "signoff SERVLET-INTEREST".
> >
> > Archives: http://archives.java.sun.com/archives/servlet-interest.html
> > Resources: http://java.sun.com/products/servlet/external-resources.html
> > LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
> >
> >
> ___________________________________________________________________________
> > To unsubscribe, send email to [EMAIL PROTECTED] and include in the
> body
> > of the message "signoff SERVLET-INTEREST".
> >
> > Archives: http://archives.java.sun.com/archives/servlet-interest.html
> > Resources: http://java.sun.com/products/servlet/external-resources.html
> > LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
>
> ___________________________________________________________________________
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
> of the message "signoff SERVLET-INTEREST".
>
> Archives: http://archives.java.sun.com/archives/servlet-interest.html
> Resources: http://java.sun.com/products/servlet/external-resources.html
> LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
>
> ___________________________________________________________________________
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
> of the message "signoff SERVLET-INTEREST".
>
> Archives: http://archives.java.sun.com/archives/servlet-interest.html
> Resources: http://java.sun.com/products/servlet/external-resources.html
> LISTSERV Help: http://www.lsoft.com/manuals/user/user.html

___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".

Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html

Reply via email to