Hi Mark,
Sorry for being so late, but I would like to get this patch in the
release, because I made some changes to IKVM class loading that exposed
the fact that Toolkit incorrectly calls ClassLoader.loadClass instead of
Class.forName (and hence failing to load my AWT toolkit).
If you'd rather not make this change this late in the release, I
understand and I'll base my IKVM release on a patched version.
Thanks,
Jeroen
2006-05-15 Jeroen Frijters <jeroen@xxxxxxxxxxxx>
* java/awt/Toolkit.java (getDefaultToolkit): Use Class.forName()
instead of directly calling the class loader.
-------------- next part --------------
Index: java/awt/Toolkit.java
===================================================================
RCS file: /cvsroot/classpath/classpath/java/awt/Toolkit.java,v
retrieving revision 1.40
diff -u -r1.40 Toolkit.java
--- java/awt/Toolkit.java 20 Apr 2006 20:06:13 -0000 1.40
+++ java/awt/Toolkit.java 15 May 2006 15:36:12 -0000
@@ -544,7 +544,7 @@
return ClassLoader.getSystemClassLoader();
}
});
- Class cls = cl.loadClass(toolkit_name);
+ Class cls = Class.forName(toolkit_name, true, cl);
Object obj = cls.newInstance();
if (!(obj instanceof Toolkit))
throw new AWTError(toolkit_name + " is not a subclass of " +
