Subject | Re: interbase.interclient.Driver ClassNotFoundException. |
---|---|
Author | traverswaker |
Post date | 2002-05-09T13:15:27Z |
--- In Firebird-Java@y..., "rrokytskyy" <rrokytskyy@y...> wrote:
had a Class-Path entry in the manifest file of my jar, and it was
causing the -classpath paramameter to the VM to be ignored.
For example:
java -classpath lib/interclient.jar -jar myprogram.jar
The VM will ignore (or overwrite?) the -classpath parameter if
myprogram.jar contains a manifest with a Class-Path entry in it.
Quite confusing.
Thanks to those who replied to my questions.
Travers
> > Despite the fact that I'm putting "interclient.jar" in myclasspath
> > (via the -classpath option to the vm from SUN SDK 1.4), I stillget
> > a ClassNotFoundException when I try:compile
> > Class.forName("interbase.interclient.Driver");
> >
> > Has anyone else had this strange problem? Does anyone have some
> > ideas about what I should try next to sort out this problem?
>
> It might be an issue with JDK 1.4. Sun changes versions of some
> classes, and usually binary code compiled for JDK 1.3 does not work
> with JDK 1.4. Try to get sources of InterClient from CVS and
> with your JDK (there's an Ant script by David Jencks that willI'm glad to report that my problem is fixed. It turned out that I
> simplify you life, but any javac will do the job).
>
> Best regards,
> Roman Rokytskyy
had a Class-Path entry in the manifest file of my jar, and it was
causing the -classpath paramameter to the VM to be ignored.
For example:
java -classpath lib/interclient.jar -jar myprogram.jar
The VM will ignore (or overwrite?) the -classpath parameter if
myprogram.jar contains a manifest with a Class-Path entry in it.
Quite confusing.
Thanks to those who replied to my questions.
Travers