Community
Participate
Working Groups
RCP & jws fails on java 1.6. the reason is that 1.6 Classloader.getResource (used in org.eclipse.core.launcher.WebStartMain.getAllJars()) behaves differently to the previous versions (1.4 & 1.5). please see http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6431929 this causes that loader.loadClass(STARTER); in org.eclipse.core.launcher.Main.invokeFramework(String[] passThruArgs, URL[] bootPath) fails.
maybe that helps: when i add the following code if (parent == null) { parent = Thread.currentThread().getContextClassLoader(); } before line URLClassLoader loader = new StartupClassLoader(bootPath, parent); in org.eclipse.core.launcher.Main.invokeFramework(String[] passThruArgs, URL[] bootPath), eclipse can load the STARTER(org.eclipse.core.runtime.adaptor.EclipseStarter) class and invoke the run method. the reason why this works is that com.sun.javaws.Main.main(final String args[]) invokes this line: Thread.currentThread().setContextClassLoader(com.sun.jnlp.JNLPClassLoader.createClassLoader()); com.sun.javaws.Main and com.sun.jnlp.JNLPClassLoader are inside $JRE$\lib\javaws.jar. com.sun.jnlp.JNLPClassLoader is the class which has changed from 1.5 to 1.6 and results the püroblem. but now it fails later on org.eclipse.osgi.framework.internal.core.Framework.findVMProfile() in line url = systemBundle.getEntry(javaProfile);. this is caused by org.eclipse.osgi.internal.baseadaptor.SystemBundleData.createBundleFile(File osgiBase) which gets a wrong osgiBase File object.
Which version of 3.2 do you use? This bug has been fixed (in a conservative way) for 3.2.2 (see bug #169691). Also, it has been fixed in 3.3, could you please confirm? Note that you should wait until the 3.3 M7 is released because of bug #170373.
ok, sorry!! i worked with 3.2.1. in 3.2.2 it works. :-) i will confirm for 3.3 after M7 release.
ok. it also works with 3.3 M7
