Launching problem

From: Emmanuel GEZE (egez..elefonica.net)
Date: Tue Sep 13 2005 - 05:30:05 EDT

  • Next message: Mike Schrag: "Re: Launching problem"

    Hi,

    I'm just installing WOLips 2.0.0.42 with Eclipse 3.1.1 (build
    M20050907-1200) and i'm not able to launch a simple WO Application.
    I create the application with the WOApplication wizard and i try to
    launch it with RunAs WOApplication.

    The result is this error message:
    "Plug-in org.objectstyle.wolips.launching was unable to load class
    org.objectstyle.wolips.launching.classpath.WORuntimeClasspathResolverimeClasspathResolver."

    Exception Stack Trace:
    "
    java.lang.ClassNotFoundException:
    org.objectstyle.wolips.launching.classpath.WORuntimeClasspathResolverimeClasspathResolver
    at
    org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:405)
    at
    org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:350)
    at
    org.eclipse.osgi.framework.adaptor.core.AbstractClassLoader.loadClass(AbstractClassLoader.java:78)
    at java.lang.ClassLoader.loadClass(Unknown Source)
    at
    org.eclipse.osgi.framework.internal.core.BundleLoader.loadClass(BundleLoader.java:275)
    at
    org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:227)
    at
    org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1248)
    at
    org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:152)
    at
    org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:142)
    at
    org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:129)
    at
    org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:48)
    at
    org.eclipse.jdt.internal.launching.RuntimeClasspathEntryResolver.getResolver(RuntimeClasspathEntryResolver.java:51)
    at
    org.eclipse.jdt.internal.launching.RuntimeClasspathEntryResolver.resolveVMInstall(RuntimeClasspathEntryResolver.java:82)
    at org.eclipse.jdt.launching.JavaRuntime.getVMInstall(JavaRuntime.java:326)
    at
    org.eclipse.jdt.launching.JavaRuntime.computeVMInstall(JavaRuntime.java:1204)
    at
    org.eclipse.jdt.launching.AbstractJavaLaunchConfigurationDelegate.getVMInstall(AbstractJavaLaunchConfigurationDelegate.java:110)
    at
    org.eclipse.jdt.launching.AbstractJavaLaunchConfigurationDelegate.verifyVMInstall(AbstractJavaLaunchConfigurationDelegate.java:182)
    at
    org.objectstyle.wolips.launching.delegates.WOJavaLocalApplicationLaunchConfigurationDelegate.launch(WOJavaLocalApplicationLaunchConfigurationDelegate.java:177)
    at
    org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:590)
    at
    org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:515)
    at
    org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:733)
    at org.eclipse.debug.internal.ui.DebugUIPlugin$6.run(DebugUIPlugin.java:931)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)
    "

    Anyone else with this problem ?

    This archive was generated by hypermail 2.0.0 : Tue Sep 13 2005 - 05:30:17 EDT