confusion when CLASSPATH includes compiled class
Andrew Haley
aph@redhat.com
Tue Mar 22 20:46:00 GMT 2005
Per Bothner writes:
> Is this a known issue?
>
> If I run a gcj-compiled application that has class Foo.java/Foo.class
> compiled and linked into the executation, with a CLASSPATH that
> includes Foo.class then things get really confused.
> A Class.forName("Foo") will load the class in the CLASSPATH.
> On the other hand other native code will reference the native-class.
This is one of the things the new ABI will fix, for sure. However, I
thought Class.forName("Foo") should find the compiled class if it's in
the executable.
Andrew.
More information about the Java
mailing list