In addition to David's solution, which is the classic one, you can also
put jt400.jar ( or any other jar ) in the jre/lib/ext directory without
specifying the specific jar.  It's a pretty good solution for tools that
will commonly be used across many applications.  You can also use your own
extension dirs, but you must then specify them as a system property.

                                                         Joe Sam

Joe Sam Shirah -
conceptGO         -        Consulting/Development/Outsourcing
Java Filter Forum:
Just the JDBC FAQs:
Going International?
Que Java400?   

----- Original Message -----
From: "David Gibbs" <david@xxxxxxxxxxxx>
To: <java400-l@xxxxxxxxxxxx>
Sent: Thursday, November 13, 2003 2:36 PM
Subject: Re: ClassNotFoundException

> Ron Anderson wrote:
> > I export the application as a JAR file, I have included the JT400.JAR
> > file within the application JAR. I have also tried just placing the
> > JT400.JAR file in the same directory as the application JAR file, but
> > receive the same error. The classpath is set to the current directory
> > (-cp .). What am I not understanding when it searches for the JDBC
> > driver? Thanks in advance.
> Your classpath needs to include the actual JAR that the JT400 classes
> live in.  Including the JT400.JAR in the application JAR does not work
> (as far as I know).  Using '-cp .' tells the JVM to only include classes
> there are in the current directory.
> If you extracted the classes from JT400.JAR and included them in your
> application jar, then it would work.
> Your classpath should look something like this ... "-classpath
> ./jt400.jar;./application.jar"
> david

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.