Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Rich Client Platform (RCP) » RCP + Java Web Start, Application doesn't launch
RCP + Java Web Start, Application doesn't launch [message #457433] Tue, 31 October 2006 17:33 Go to next message
Eclipse UserFriend
Originally posted by: pi.trash-mail.de

Hi,
I want to deploy a RCP Application via Web Start. I read the exlipse help about that subject, but I don't get it to work. I created a wrapper feature for the RCP application, exported the feature as jar files and signed them. Then I created the JNLP start file.

When I open the JNLP file in a browser, Java Web Start finds all the jars and downloads them and asks for the permission to start the application. But after that nothing happens. I consulted the Web Start Log files but they are empty. I have no idea if the startup.jar is even executed?

I don't know where I should start to look, to solve this problem. If anyone has had the same problems and solved them, or has an idea where I should start to look for the cause of this problem, I would be very thankful for suggestions. Also if you know some good resources to get started with RCP and Web Start I would appreciate if you would post the links.

I programmed a little hello world swing jframe app and started it via Web Start, it worked without problems. I also tried to start the RCP mail template application with Web Start, but that didn't work.

Pyoeter
Re: RCP + Java Web Start, Application doesn't launch [message #457441 is a reply to message #457433] Tue, 31 October 2006 17:59 Go to previous messageGo to next message
Alex Blewitt is currently offline Alex BlewittFriend
Messages: 946
Registered: July 2009
Senior Member
What does your JNLP file look like? Do you list all of the requirements, including the native bundles for your OS or the startup.jar? My guess is that you're missing some key parts out of the JNLP, but it's a bit difficult to know what without seeing it...

Alex.
Re: RCP + Java Web Start, Application doesn't launch [message #457443 is a reply to message #457441] Tue, 31 October 2006 18:15 Go to previous messageGo to next message
Peter Rutsch is currently offline Peter RutschFriend
Messages: 19
Registered: July 2009
Junior Member
Thanks for your reply! This is how my JNLP file looks like.
 
<?xml version="1.0" encoding="UTF-8"?>
<jnlp 
    spec="1.0+" 
    codebase="file:///home/prutsch/bin" 
    href="XXXX.jnlp"> <!-- URL to the site containing the jnlp application. It should match the value used on  export. Href, the name of this file -->
  <information>
    <!-- user readable name of the application -->
    <title> XXXX </title>  
    <!-- vendor name -->
    <vendor>XXXX</vendor>
    <!-- vendor homepage --> 
    <homepage href="http://www.xxxx.com" /> 
    <!-- product description -->
    <description>GUI Aplication</description> 
    <icon kind="splash" href="splash.gif"/>
  </information>
 
  <!--request all permissions from the application. This does not change-->
  <security>
    <all-permissions/>
  </security>
 
  <!-- The name of the main class to execute. This does not change-->
  <application-desc main-class="org.eclipse.core.launcher.WebStartMain">
   <!-- <argument>-nosplash</argument>-->
  </application-desc>
 
  <resources>
    <!-- Reference to the startup.jar. This does not change -->
    <jar href="startup.jar"/>
 
    <!-- Reference to all the plugins and features constituting the application -->
    <!-- Here we are referring to the wrapper feature since it transitively refers to all the other plug-ins  necessary -->
    <extension 
        name="Wrapper feature"
        href="features/com.XXXX.XXXX.feature_1.0.0.jnlp"/>
    <!-- Information usually specified in the config.ini -->
    <property 
        name="osgi.instance.area" 
        value="@user.home/Application Data/XXXX"/>
    <property 
        name="osgi.configuration.area" 
        value="@user.home/Application Data/XXXX"/>
        
    <!-- The id of the product to run, like found in the overview page of the product editor-->
    <property 
        name="eclipse.product" 
        value="com.XXXX.XXXX.product"/> 
  </resources>

  <!-- Indicate on a platform basis which JRE to use --> 
  <resources os="Mac">
    <j2se version="1.5+" java-vm-args="-XstartOnFirstThread"/>
  </resources>
  <resources os="Windows">
    <j2se version="1.5+"/>
  </resources>
  <resources os="Linux">
    <j2se version="1.5+"/>
  </resources>
</jnlp>
Re: RCP + Java Web Start, Application doesn't launch [message #457445 is a reply to message #457443] Tue, 31 October 2006 18:36 Go to previous messageGo to next message
Alex Blewitt is currently offline Alex BlewittFriend
Messages: 946
Registered: July 2009
Senior Member
So far so good ... but what about the feature.jnlp?

Alex.
Re: RCP + Java Web Start, Application doesn't launch [message #457446 is a reply to message #457445] Tue, 31 October 2006 19:02 Go to previous messageGo to next message
Peter Rutsch is currently offline Peter RutschFriend
Messages: 19
Registered: July 2009
Junior Member
JNLP file of feature 1:
 <?xml version="1.0" encoding="UTF-8"?>
<jnlp spec="1.0+" codebase="file:///home/prutsch/bin">
	<information>
		<title>XXXX Feature</title>
		<vendor>XXXX</vendor>
		<offline-allowed/>
	</information>
	<security>
		<all-permissions/>
	</security>
	<component-desc/>
	<resources>
		<j2se version="1.5+" />
	</resources>
	<resources>
		<extension href="features/org.eclipse.rcp_3.2.0.v20060609m-SVDNgVrNoh-MeGG.jnlp" />
		<jar href="plugins/com.XXXX.XXXX_1.0.0.jar"/>
		<jar href="plugins/com.XXXX.XXXX_1.0.0.jar"/>
		<jar href="plugins/org.hibernate.eclipse_3.1.0.jar"/>
		<jar href="plugins/com.mysql.eclipse_3.1.0.jar"/>
		<jar href="plugins/org.eclipse.swt_3.2.0.v3232o.jar"/>
	</resources>
</jnlp> 


and feature 2 is the org.eclipse.rcp feature:
 
<?xml version="1.0" encoding="UTF-8"?>
<jnlp spec="1.0+" codebase="file:///home/prutsch/bin">
	<information>
		<title>%featureName</title>
		<vendor>%providerName</vendor>
		<offline-allowed/>
	</information>
	<security>
		<all-permissions/>
	</security>
	<component-desc/>
	<resources>
		<j2se version="1.5+" />
	</resources>
	<resources>
		<jar href="plugins/com.ibm.icu_3.4.4.1.jar"/>
		<jar href="plugins/org.eclipse.core.commands_3.2.0.I20060605-1400.jar"/>
		<jar href="plugins/org.eclipse.core.jobs_3.2.0.v20060603.jar"/>
		<jar href="plugins/org.eclipse.core.expressions_3.2.0.v20060605-1400.jar"/>
		<jar href="plugins/org.eclipse.core.runtime_3.2.0.v20060603.jar"/>
		<jar href="plugins/org.eclipse.core.runtime.compatibility.auth_3.2.0.v20060601.jar"/>
		<jar href="plugins/org.eclipse.osgi_3.2.0.v20060601.jar"/>
		<jar href="plugins/org.eclipse.help_3.2.0.v20060602.jar"/>
		<jar href="plugins/org.eclipse.swt_3.2.0.v3232o.jar"/>
		<jar href="plugins/org.eclipse.jface_3.2.0.I20060605-1400.jar"/>
		<jar href="plugins/org.eclipse.jface.databinding_1.0.0.I20060605-1400.jar"/>
		<jar href="plugins/org.eclipse.ui_3.2.0.I20060605-1400.jar"/>
		<jar href="plugins/org.eclipse.ui.workbench_3.2.0.I20060605-1400.jar"/>
		<jar href="plugins/org.eclipse.update.configurator_3.2.0.v20060605.jar"/>
	</resources>
	<resources os="Windows" arch="x86">
		<jar href="plugins/org.eclipse.swt.win32.win32.x86_3.2.0.v3232m.jar"/>
	</resources>
	<resources os="Linux" arch="x86">
		<jar href="plugins/org.eclipse.swt.gtk.linux.x86_3.2.0.v3232m.jar"/>
	</resources>
	<resources os="Solaris" arch="sparc">
		<jar href="plugins/org.eclipse.swt.gtk.solaris.sparc_3.2.0.v3232m.jar"/>
	</resources>
	<resources os="Solaris" arch="x86">
		<jar href="plugins/org.eclipse.swt.gtk.solaris.x86_3.2.0.HEAD.jar"/>
	</resources>
	<resources os="Linux" arch="ppc">
		<jar href="plugins/org.eclipse.swt.gtk.linux.ppc_3.2.0.v3232m.jar"/>
	</resources>
	<resources os="Linux" arch="x86_64">
		<jar href="plugins/org.eclipse.swt.gtk.linux.x86_64_3.2.0.v3232m.jar"/>
	</resources>
	<resources os="Mac">
		<jar href="plugins/org.eclipse.swt.carbon.macosx_3.2.0.v3232m.jar"/>
	</resources>
	<resources os="AIX" arch="ppc">
		<jar href="plugins/org.eclipse.swt.motif.aix.ppc_3.2.0.v3232m.jar"/>
	</resources>
	<resources os="HP-UX" arch="PA_RISC">
		<jar href="plugins/org.eclipse.swt.motif.hpux.PA_RISC_3.2.0.v3232m.jar"/>
	</resources>
	<resources os="Linux" arch="x86">
		<jar href="plugins/org.eclipse.swt.motif.linux.x86_3.2.0.v3232m.jar"/>
	</resources>
	<resources os="Linux" arch="ia64">
		<jar href="plugins/org.eclipse.swt.gtk.linux.ia64_3.2.0.HEAD.jar"/>
	</resources>
	<resources os="Solaris" arch="sparc">
		<jar href="plugins/org.eclipse.swt.motif.solaris.sparc_3.2.0.v3232m.jar"/>
	</resources>
	<resources os="qnx" arch="x86">
		<jar href="plugins/org.eclipse.swt.photon.qnx.x86_3.2.0.v3232m.jar"/>
	</resources>
	<resources os="HP-UX" arch="ia64_32">
		<jar href="plugins/org.eclipse.swt.motif.hpux.ia64_32_3.2.0.HEAD.jar"/>
	</resources>
	<resources>
		<jar href="plugins/org.eclipse.rcp_3.2.0.v20060605.jar"/>
		<jar href="plugins/org.eclipse.core.contenttype_3.2.0.v20060603.jar"/>
		<jar href="plugins/org.eclipse.equinox.common_3.2.0.v20060603.jar"/>
		<jar href="plugins/org.eclipse.equinox.preferences_3.2.0.v20060601.jar"/>
		<jar href="plugins/org.eclipse.equinox.registry_3.2.0.v20060601.jar"/>
	</resources>
</jnlp>
Re: RCP + Java Web Start, Application doesn't launch [message #457451 is a reply to message #457446] Tue, 31 October 2006 21:49 Go to previous messageGo to next message
Alex Blewitt is currently offline Alex BlewittFriend
Messages: 946
Registered: July 2009
Senior Member
Isn't there some kind of directory issue here? The JNLP from the first one is listed as features/com.example.jnlp,and the JNLP from the second includes features/rcp.jnlp. If those directories are transitive, wouldn't you get features/features/rcp.jnlp on the server? It's not clear if that's the case.

Does the client download all of the Jars? I think that Java WebStart caches the downloaded jars, and you could see whether they've downloaded the right ones (or into the right locations). You can also check on the webserver's logs whether the jars were served by your webserver.

Alex.
Re: RCP + Java Web Start, Application doesn't launch [message #457453 is a reply to message #457451] Tue, 31 October 2006 22:29 Go to previous messageGo to next message
Peter Rutsch is currently offline Peter RutschFriend
Messages: 19
Registered: July 2009
Junior Member
First, yes I think Java Web Start downloads everything correctly. I looked into the /myhome/.java/deployment/cache/... directory and all the jars and jnlp files are downloaded into the right location. All with a "DM" prefix.

If I understand my JNLP files right, then the "MAIN" JNLP file addresses the wrapper feature which is located in file:///home/prutsch/bin/features/com.XXXX.XXXX.feature_1.0. 0.jnlp

The JNLP file for the wrapper feature (which is the JNLP file of feature 1), then points to the second feature, the rcp feature which is located in file:///home/prutsch/bin/features/org.eclipse.rcp_3.2.0.v200 60609m-SVDNgVrNoh-MeGG.jnlp"

So if the address always starts with the code base and then adds the address that is written in the extension href"...", it should find everything.

Strange is also, that in the cache directory, no configuration directory is created when I start the application via Web Start. If I do it by hand with "java -jar /cachelocation/RMstartup.jar" then it creates the configuration directory and logs an error
 java.lang.RuntimeException: Could not find framework
	at org.eclipse.core.launcher.Main.getBootPath(Main.java:639)
	at org.eclipse.core.launcher.Main.basicRun(Main.java:274)
	at org.eclipse.core.launcher.Main.run(Main.java:977)
	at org.eclipse.core.launcher.Main.main(Main.java:952)
Which isn't surprising.

So I have the impression, that nothing happens, after downloading everything needed. The only thing that happens, is that the Web Start Console appears for a few seconds and then disappars again.

Thank you for taking the time looking at the JNLP Files.

Pyoeter
Re: RCP + Java Web Start, Application doesn't launch [message #457455 is a reply to message #457453] Wed, 01 November 2006 00:01 Go to previous messageGo to next message
Alex Blewitt is currently offline Alex BlewittFriend
Messages: 946
Registered: July 2009
Senior Member
I'm not sure if using file:/// URLs would be the cause of the problem ... it's a possibility. You should download something like e.g. Apache and try serving the JNLP files via HTTP to see if that makes any difference. (You'll then be able to track whether they're being downloaded, too.)

Running startup.jar with java -jar won't work -- there's two classes in there; Main, and WebStartMain. It's the latter that gets called as part of the webstart process, but Main is the one listed as the Main-Class in the startup jar. That's what the 'application-desc main-class="org.eclipse.core.launcher.WebStartMain"' is doing in the JNLP file.

You could try running it on the command line with something like:

java -Dosgi.instance.area=/tmp/workspace -Dosgi.configuration.area=/tmp/config -cp startup.jar org.eclipse.core.launcher.WebStartMain

to see what other error messages get logged. Alternatively, you could try changing your osgi.instance.area and osgi.configuration.area to different locations e.g. /tmp to ensure it's not a permissioning issue.

Oh, and you've also commented out the -nosplash. Does it work when you have the -nosplash argument?

Lastly, you're not running on a Mac, are you? There's known problems with JNLP and Macs ...

Alex
Re: RCP + Java Web Start, Application doesn't launch [message #457481 is a reply to message #457455] Wed, 01 November 2006 15:24 Go to previous messageGo to next message
Peter Rutsch is currently offline Peter RutschFriend
Messages: 19
Registered: July 2009
Junior Member
Thank you very much! I have now some log files of the application. It was my fault, I didn't understand these lines in the JNLP file:
<property 
        name="osgi.instance.area" 
        value="/tmp/workspace"/>
<property 
        name="osgi.configuration.area" 
        value="/tmp/config"/>

The second determines the configuration folder, where the log files are located. I didn't know that and didn't look. That's what happens when you don't know what you are doing and just copy stuff from other people. :-)

Anyways, this is the error message I have got now. I think that should help me to fix the problem. Thank you again very much for giving me the hints.

Peter


!SESSION 2006-11-01 10:00:10.793 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.5.0_06
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=motif, NL=en_CA

!ENTRY org.eclipse.core.runtime 2006-11-01 10:00:12.203
!MESSAGE Product com.xxxx.xxxx.manager.product could not be found.

!ENTRY org.eclipse.osgi 4 0 2006-11-01 10:00:12.210
!MESSAGE Application error
!STACK 1
java.lang.RuntimeException: No application id has been found.
	at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:56)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
	at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
	at org.eclipse.core.launcher.WebStartMain.basicRun(WebStartMain.java:59)
	at org.eclipse.core.launcher.Main.run(Main.java:977)
	at org.eclipse.core.launcher.WebStartMain.main(WebStartMain.java:40)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at com.sun.javaws.Launcher.executeApplication(Launcher.java:1154)
	at com.sun.javaws.Launcher.executeMainClass(Launcher.java:1101)
	at com.sun.javaws.Launcher.continueLaunch(Launcher.java:944)
	at com.sun.javaws.Launcher.handleApplicationDesc(Launcher.java:515)
	at com.sun.javaws.Launcher.handleLaunchFile(Launcher.java:218)
	at com.sun.javaws.Launcher.run(Launcher.java:165)
	at java.lang.Thread.run(Thread.java:595)

!ENTRY org.eclipse.osgi 2 0 2006-11-01 10:00:12.220
!MESSAGE One or more bundles are not resolved because the following root constraints are not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2006-11-01 10:00:12.220
!MESSAGE Bundle initial@reference:file:DMplugins/RMcom.xxxx.xxxx.manager_1.0.0.jar/ was not resolved.
!SUBENTRY 2 com.xxxx.xxxx.manager 2 0 2006-11-01 10:00:12.220
!MESSAGE Missing required bundle org.eclipse.ui.forms_0.0.0.
!SUBENTRY 2 com.xxxx.xxxx.manager 2 0 2006-11-01 10:00:12.221
!MESSAGE Missing required bundle org.eclipse.pde.runtime_0.0.0.

!ENTRY org.eclipse.osgi 2 0 2006-11-01 10:00:12.222
!MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists:
!SUBENTRY 1 org.eclipse.osgi 2 0 2006-11-01 10:00:12.222
!MESSAGE Bundle initial@reference:file:DMplugins/RMcom.xxxx.xxxx.manager_1.0.0.jar/ [31] was not resolved.
!SUBENTRY 2 com.xxxx.xxxx.manager 2 0 2006-11-01 10:00:12.222
!MESSAGE Missing required bundle org.eclipse.ui.forms_0.0.0.
!SUBENTRY 2 com.xxxx.xxxx.manager 2 0 2006-11-01 10:00:12.222
!MESSAGE Missing required bundle org.eclipse.pde.runtime_0.0.0.

Re: RCP + Java Web Start, Application doesn't launch [message #457486 is a reply to message #457481] Wed, 01 November 2006 16:37 Go to previous messageGo to next message
Alex Blewitt is currently offline Alex BlewittFriend
Messages: 946
Registered: July 2009
Senior Member
Yup, that shows you what's wrong:

!MESSAGE Bundle initial@reference:file:DMplugins/RMcom.xxxx.xxxx.manager_1.0.0.jar/ [31] was not resolved.
!SUBENTRY 2 com.xxxx.xxxx.manager 2 0 2006-11-01 10:00:12.222
!MESSAGE Missing required bundle org.eclipse.ui.forms_0.0.0.
!SUBENTRY 2 com.xxxx.xxxx.manager 2 0 2006-11-01 10:00:12.222
!MESSAGE Missing required bundle org.eclipse.pde.runtime_0.0.0.


Your com.xxx.xxx.manager_1.0.0 depends on org.eclipse.ui.forms and (for some reason) org.eclipse.pde.runtime, but you're not shipping those with your RCP bundle. You'll need to ship both of these (note: and their dependencies) in one (or more) of your JNLP files in order for them to be found. Once you do that, the bundle might stand a chance of starting, and if it's where your application resides, your app might start up.

Alex.
Re: RCP + Java Web Start, Application doesn't launch [message #457491 is a reply to message #457486] Wed, 01 November 2006 18:04 Go to previous messageGo to next message
Peter Rutsch is currently offline Peter RutschFriend
Messages: 19
Registered: July 2009
Junior Member
I think I'm getting closer and closer :-)
I removed the strange pde.runtime dependency and added ui.forms to the required plug-ins in the feature. This is what I have got now.

!SESSION 2006-11-01 12:49:47.381 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.5.0_06
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=motif, NL=en_CA

!ENTRY org.eclipse.osgi 4 0 2006-11-01 12:49:48.804
!MESSAGE An error occurred while automatically activating bundle org.eclipse.ui.workbench (25).
!STACK 0
org.osgi.framework.BundleException: The activator org.eclipse.ui.internal.WorkbenchPlugin for bundle org.eclipse.ui.workbench is invalid
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:141)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:966)
	at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:317)
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:256)
	at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.preFindLocalClass(EclipseLazyStarter.java:86)
	at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:409)
	at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:188)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:339)
	at org.eclipse.osgi.framework.internal.core.SingleSourcePackage.loadClass(SingleSourcePackage.java:37)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:388)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:352)
	at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:83)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
	at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
	at java.lang.ClassLoader.defineClass1(Native Method)
	at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
	at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.defineClass(DefaultClassLoader.java:160)
	at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.defineClass(ClasspathManager.java:498)
	at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findClassImpl(ClasspathManager.java:468)
	at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClassImpl(ClasspathManager.java:427)
	at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:410)
	at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:188)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:339)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:391)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:352)
	at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:83)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.loadClass(BundleLoader.java:276)
	at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:227)
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:134)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:966)
	at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:317)
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:256)
	at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.preFindLocalClass(EclipseLazyStarter.java:86)
	at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:409)
	at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:188)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:339)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:391)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:352)
	at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:83)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.loadClass(BundleLoader.java:276)
	at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:227)
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1245)
	at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:147)
	at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:759)
	at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
	at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:51)
	at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:74)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
	at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
	at org.eclipse.core.launcher.WebStartMain.basicRun(WebStartMain.java:59)
	at org.eclipse.core.launcher.Main.run(Main.java:977)
	at org.eclipse.core.launcher.WebStartMain.main(WebStartMain.java:40)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at com.sun.javaws.Launcher.executeApplication(Launcher.java:1154)
	at com.sun.javaws.Launcher.executeMainClass(Launcher.java:1101)
	at com.sun.javaws.Launcher.continueLaunch(Launcher.java:944)
	at com.sun.javaws.Launcher.handleApplicationDesc(Launcher.java:515)
	at com.sun.javaws.Launcher.handleLaunchFile(Launcher.java:218)
	at com.sun.javaws.Launcher.run(Launcher.java:165)
	at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NoClassDefFoundError: org/eclipse/swt/SWTError
	at java.lang.Class.getDeclaredConstructors0(Native Method)
	at java.lang.Class.privateGetDeclaredConstructors(Class.java:2328)
	at java.lang.Class.getConstructor0(Class.java:2640)
	at java.lang.Class.newInstance0(Class.java:321)
	at java.lang.Class.newInstance(Class.java:303)
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:136)
	.xxxx.. 72 more
Root exception:
java.lang.NoClassDefFoundError: org/eclipse/swt/SWTError
	at java.lang.Class.getDeclaredConstructors0(Native Method)
	at java.lang.Class.privateGetDeclaredConstructors(Class.java:2328)
	at java.lang.Class.getConstructor0(Class.java:2640)
	at java.lang.Class.newInstance0(Class.java:321)
	at java.lang.Class.newInstance(Class.java:303)
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:136)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:966)
	at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:317)
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:256)
	at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.preFindLocalClass(EclipseLazyStarter.java:86)
	at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:409)
	at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:188)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:339)
	at org.eclipse.osgi.framework.internal.core.SingleSourcePackage.loadClass(SingleSourcePackage.java:37)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:388)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:352)
	at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:83)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
	at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
	at java.lang.ClassLoader.defineClass1(Native Method)
	at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
	at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.defineClass(DefaultClassLoader.java:160)
	at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.defineClass(ClasspathManager.java:498)
	at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findClassImpl(ClasspathManager.java:468)
	at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClassImpl(ClasspathManager.java:427)
	at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:410)
	at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:188)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:339)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:391)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:352)
	at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:83)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.loadClass(BundleLoader.java:276)
	at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:227)
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:134)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:966)
	at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:317)
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:256)
	at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.preFindLocalClass(EclipseLazyStarter.java:86)
	at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:409)
	at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:188)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:339)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:391)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:352)
	at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:83)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.loadClass(BundleLoader.java:276)
	at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:227)
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1245)
	at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:147)
	at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:759)
	at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
	at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:51)
	at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:74)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
	at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
	at org.eclipse.core.launcher.WebStartMain.basicRun(WebStartMain.java:59)
	at org.eclipse.core.launcher.Main.run(Main.java:977)
	at org.eclipse.core.launcher.WebStartMain.main(WebStartMain.java:40)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at com.sun.javaws.Launcher.executeApplication(Launcher.java:1154)
	at com.sun.javaws.Launcher.executeMainClass(Launcher.java:1101)
	at com.sun.javaws.Launcher.continueLaunch(Launcher.java:944)
	at com.sun.javaws.Launcher.handleApplicationDesc(Launcher.java:515)
	at com.sun.javaws.Launcher.handleLaunchFile(Launcher.java:218)
	at com.sun.javaws.Launcher.run(Launcher.java:165)
	at java.lang.Thread.run(Thread.java:595)

!ENTRY org.eclipse.osgi 4 0 2006-11-01 12:49:48.808
!MESSAGE An error occurred while automatically activating bundle com.xxxx.xxxx.manager (31).
!STACK 0
org.osgi.framework.BundleException: The activator com.xxxx.xxxx.manager.Activator for bundle com.xxxx.xxxx.manager is invalid
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:141)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:966)
	at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:317)
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:256)
	at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.preFindLocalClass(EclipseLazyStarter.java:86)
	at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:409)
	at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:188)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:339)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:391)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:352)
	at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:83)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.loadClass(BundleLoader.java:276)
	at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:227)
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1245)
	at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:147)
	at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:759)
	at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
	at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:51)
	at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:74)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
	at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
	at org.eclipse.core.launcher.WebStartMain.basicRun(WebStartMain.java:59)
	at org.eclipse.core.launcher.Main.run(Main.java:977)
	at org.eclipse.core.launcher.WebStartMain.main(WebStartMain.java:40)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at com.sun.javaws.Launcher.executeApplication(Launcher.java:1154)
	at com.sun.javaws.Launcher.executeMainClass(Launcher.java:1101)
	at com.sun.javaws.Launcher.continueLaunch(Launcher.java:944)
	at com.sun.javaws.Launcher.handleApplicationDesc(Launcher.java:515)
	at com.sun.javaws.Launcher.handleLaunchFile(Launcher.java:218)
	at com.sun.javaws.Launcher.run(Launcher.java:165)
	at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NoClassDefFoundError: org/eclipse/ui/plugin/AbstractUIPlugin
	at java.lang.ClassLoader.defineClass1(Native Method)
	at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
	at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.defineClass(DefaultClassLoader.java:160)
	at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.defineClass(ClasspathManager.java:498)
	at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findClassImpl(ClasspathManager.java:468)
	at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClassImpl(ClasspathManager.java:427)
	at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:410)
	at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:188)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:339)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:391)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:352)
	at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:83)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.loadClass(BundleLoader.java:276)
	at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:227)
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:134)
	.xxxx.. 43 more
Root exception:
java.lang.NoClassDefFoundError: org/eclipse/ui/plugin/AbstractUIPlugin
	at java.lang.ClassLoader.defineClass1(Native Method)
	at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
	at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.defineClass(DefaultClassLoader.java:160)
	at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.defineClass(ClasspathManager.java:498)
	at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findClassImpl(ClasspathManager.java:468)
	at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClassImpl(ClasspathManager.java:427)
	at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:410)
	at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:188)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:339)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:391)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:352)
	at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:83)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.loadClass(BundleLoader.java:276)
	at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:227)
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:134)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:966)
	at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:317)
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:256)
	at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.preFindLocalClass(EclipseLazyStarter.java:86)
	at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:409)
	at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:188)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:339)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:391)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:352)
	at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:83)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.loadClass(BundleLoader.java:276)
	at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:227)
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1245)
	at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:147)
	at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:759)
	at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
	at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:51)
	at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:74)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
	at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
	at org.eclipse.core.launcher.WebStartMain.basicRun(WebStartMain.java:59)
	at org.eclipse.core.launcher.Main.run(Main.java:977)
	at org.eclipse.core.launcher.WebStartMain.main(WebStartMain.java:40)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at com.sun.javaws.Launcher.executeApplication(Launcher.java:1154)
	at com.sun.javaws.Launcher.executeMainClass(Launcher.java:1101)
	at com.sun.javaws.Launcher.continueLaunch(Launcher.java:944)
	at com.sun.javaws.Launcher.handleApplicationDesc(Launcher.java:515)
	at com.sun.javaws.Launcher.handleLaunchFile(Launcher.java:218)
	at com.sun.javaws.Launcher.run(Launcher.java:165)
	at java.lang.Thread.run(Thread.java:595)

!ENTRY org.eclipse.osgi 4 0 2006-11-01 12:49:48.812
!MESSAGE Application error
!STACK 1
org.eclipse.core.runtime.CoreException: Plug-in com.xxxx.xxxx.manager was unable to load class com.xxxx.xxxx.manager.Application.
	at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.throwException(RegistryStrategyOSGI.java:165)
	at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:149)
	at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:759)
	at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
	at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:51)
	at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:74)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
	at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
	at org.eclipse.core.launcher.WebStartMain.basicRun(WebStartMain.java:59)
	at org.eclipse.core.launcher.Main.run(Main.java:977)
	at org.eclipse.core.launcher.WebStartMain.main(WebStartMain.java:40)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at com.sun.javaws.Launcher.executeApplication(Launcher.java:1154)
	at com.sun.javaws.Launcher.executeMainClass(Launcher.java:1101)
	at com.sun.javaws.Launcher.continueLaunch(Launcher.java:944)
	at com.sun.javaws.Launcher.handleApplicationDesc(Launcher.java:515)
	at com.sun.javaws.Launcher.handleLaunchFile(Launcher.java:218)
	at com.sun.javaws.Launcher.run(Launcher.java:165)
	at java.lang.Thread.run(Thread.java:595)
org.eclipse.core.runtime.CoreException[1]: java.lang.ClassNotFoundException: com.xxxx.xxxx.manager.Application
	at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:407)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:352)
	at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:83)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.loadClass(BundleLoader.java:276)
	at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:227)
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1245)
	at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:147)
	at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:759)
	at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
	at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:51)
	at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:74)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
	at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
	at org.eclipse.core.launcher.WebStartMain.basicRun(WebStartMain.java:59)
	at org.eclipse.core.launcher.Main.run(Main.java:977)
	at org.eclipse.core.launcher.WebStartMain.main(WebStartMain.java:40)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at com.sun.javaws.Launcher.executeApplication(Launcher.java:1154)
	at com.sun.javaws.Launcher.executeMainClass(Launcher.java:1101)
	at com.sun.javaws.Launcher.continueLaunch(Launcher.java:944)
	at com.sun.javaws.Launcher.handleApplicationDesc(Launcher.java:515)
	at com.sun.javaws.Launcher.handleLaunchFile(Launcher.java:218)
	at com.sun.javaws.Launcher.run(Launcher.java:165)
	at java.lang.Thread.run(Thread.java:595)
Re: RCP + Java Web Start, Application doesn't launch [message #457518 is a reply to message #457491] Wed, 01 November 2006 21:12 Go to previous messageGo to next message
Peter Rutsch is currently offline Peter RutschFriend
Messages: 19
Registered: July 2009
Junior Member
I wanted to explain the basic steps that I do to create a Web Start RCP application. Just in case that I do something completely wrong:
<UL>
<LI>create plug in project - RCP Hello World Template
<LI>create product configuration
<LI>add required plug-ins to configuration
<LI>try launching the product - works!
<LI>export product with export wizard - try launching the exported project - works!
<LI>sign the created startup.jar
<LI>create a feature (hello world feature)that depends on the hello world plug-in
<UL>
<LI>add the org.eclipse.rcp feature to the included features
</UL>
</LI>
<LI>create another feature, the wrapper feature for web start
<UL>
<LI>under included features add the "hello world feature"
<LI>create a directory "rootfiles", place the signed startup.jar in the rootfiles directory
<LI>change the first line of the build.properties file into root=rootfiles
</UL>
</LI>
<LI>Export the wrapper feature as a deployable feature
<LI>create a jnlp file
<LI>launch the application via the browser
</UL>
The result is that the application downloads, but doesn't start and it gives the same log file as the one that I have posted before.

Has someone any more ideas? Or am I missing a step?

I'm going to continue doing some more tests, but I have really no idea where I should continue to search for the cause.

Thank you for taking the time!
Pyoeter
Re: RCP + Java Web Start, Application doesn't launch [message #457521 is a reply to message #457518] Wed, 01 November 2006 23:32 Go to previous messageGo to next message
Alex Blewitt is currently offline Alex BlewittFriend
Messages: 946
Registered: July 2009
Senior Member
Your 'add required plugins to the configuration' is adding things that you aren't making explicitly clear in your feature setup. As a result, your feature doesn't contain all the plugins.

In the examples, look for ClassNotFoundErrors, such as

java.lang.NoClassDefFoundError: org/eclipse/swt/SWTError

That's a clue that it's not finding/downloading the org.eclipse.swt plugin or one of its dependencies (but since SWT doesn't depend on anything else, probably that that isn't being found).

Are you sure you've got the right version of the SWT? The versions look different in the fragments vs the plugins:

<jar href="plugins/org.eclipse.swt_3.2.0.v3232o.jar"/>
  :
<jar href="plugins/org.eclipse.swt.win32.win32.x86_3.2.0.v3232m.jar"/>


Note that one ends in 'o' and the other ends in 'm'. This may be the desired outcome, or it may not. You should also check in the product directory what the versions of each of the bundles is; it's quite possible that when running internally, you're running against a slightly different (e.g. updated) version of Eclipse.

To find out what bundles aren't starting, try running the set of jars from the command line with:

java -Dosgi.configuration.area=... -Dosgi.instance.area=... -jar startup.jar -console -noExit

That will bring you into the OSGi console (? is help) and you can then issue a 'ss' to find out what bundles are installed, or cannot be resolved. 'diag' will give you more information.

If you've got bundle incompatibilities (or missing bundles) then this will help give you a clue.

Also, try creating a new launch configuration and *only* enable the RCP and XXX feature. If it doesn't run like that, you've got some missing dependencies in your features you need to fix.

Alex.
Re: RCP + Java Web Start, Application doesn't launch [message #457523 is a reply to message #457521] Wed, 01 November 2006 23:51 Go to previous messageGo to next message
Peter Rutsch is currently offline Peter RutschFriend
Messages: 19
Registered: July 2009
Junior Member
Thank you for your reply and the new ideas. I'm going to look into that tomorrow.

I continued testing today and tried the following:

Based on the scenario I described above, I placed a product configuration file in the "hello world feature" and made the product "based on features". The rest remained the same, the "hello world feature" still depends on the "hello word plugin" and on the org.eclipse.rcp feature.

When I exported the product and executed the resulting RCP application, it didn't start and I got the exact same error again, that it can't find some bundles. This time without Web Start.
Re: RCP + Java Web Start, Application doesn't launch [message #457524 is a reply to message #457523] Thu, 02 November 2006 00:05 Go to previous messageGo to next message
Alex Blewitt is currently offline Alex BlewittFriend
Messages: 946
Registered: July 2009
Senior Member
Try running this with the -console and -noExit flags, and use the OSGi console to list what's there. You might find that you've not included everything you need in your main feature, or that the SWT is out of date. Are you running on e.g. 3.2.1 which you upgraded from 3.2.0? If so, consider downloading a fresh copy of 3.2.1 and then setting up a different workspace, then import your projects in again. At least then you'll know whether you've got a consistent set of plugins, if not a complete set.

You can also try to create a new (empty) launch config in PDE, and *just* add the features, and try to startup. With any luck, that shouldn't work. Take a note of all the plugins that are selected, and then click on 'validate plugins' -- it should give you a warning if there are any missing. If that doesn't work, try to add required bundles and then see what's different. Chances are, you're just missing something that the PDE can help with.

Lastly, check the RCP feature that you're exporting it with. If you've got an RCP feature from 3.2.0, but have 3.2.1 installed (or vice versa), you might get problems since the version numbers won't match exactly.

Alex.
Re: RCP + Java Web Start, Application doesn't launch [message #457579 is a reply to message #457524] Thu, 02 November 2006 18:45 Go to previous messageGo to next message
Peter Rutsch is currently offline Peter RutschFriend
Messages: 19
Registered: July 2009
Junior Member
Just a short report what is going on. I downloaded and installed the Eclipse Version 3.3.0 Build id: I20060922-0010. First small success: I can now export a product that is based on features and run it.

I tested to run the startup.jar of this exported product with the command you told me (java -Dosgi.configuration.area=... -Dosgi.instance.area=... -jar startup.jar -console -noExit ). It doesn't start the application. What I got in the osgi console is this
Framework is launched.

id      State       Bundle
0       ACTIVE      system.bundle_3.3.0.v20060919
32      ACTIVE      org.eclipse.equinox.common_3.3.0.v20060906
33      ACTIVE      org.eclipse.update.configurator_3.2.0.v20092006-1400
34      ACTIVE      org.eclipse.core.runtime_3.2.100.v20060905
35      RESOLVED    test.rcphellowebstart_1.0.0
36      ACTIVE      org.eclipse.core.runtime.compatibility.auth_3.2.0.v20060717
37      RESOLVED    org.eclipse.jface_3.3.0.I20060921-0010
38      ACTIVE      org.eclipse.equinox.registry_3.2.100.v20060918
40      RESOLVED    com.ibm.icu_3.4.4.1
41      RESOLVED    org.eclipse.core.commands_3.2.0.I20060918-0010
43      RESOLVED    org.eclipse.rcp_3.2.0.v20060605
44      RESOLVED    org.eclipse.jface.databinding_1.0.100.I20060918-0010
46      RESOLVED    org.eclipse.ui.workbench_3.3.0.I20060921-0010
47      RESOLVED    org.eclipse.core.expressions_3.2.0.v20060920-1200
48      RESOLVED    org.eclipse.core.contenttype_3.2.100.v20060808
49      ACTIVE      org.eclipse.core.jobs_3.2.0.v20060731
51      RESOLVED    org.eclipse.swt_3.3.0.v3309a
52      RESOLVED    org.eclipse.ui_3.3.0.I20060921-0010
53      RESOLVED    org.eclipse.help_3.3.0.v20060915
54      INSTALLED   org.eclipse.swt.gtk.linux.x86_3.3.0.v3309
55      ACTIVE      org.eclipse.equinox.preferences_3.2.100.v20060918

Remark that org.eclipse.swt.gtk.linux.x86_3.3.0.v3309 is only installed not resolved or active. If I execute the compiled launcher and look at the osgi console the application runs and this package is marked as resolved.

Then I looked at the log file it created. The following is the output

!SESSION 2006-11-02 12:15:55.397 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.5.0_06
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=motif, NL=en_CA
Command-line arguments:  -console

..
**Error messages like in one of the previous posts**
..
..
!ENTRY org.eclipse.osgi 2 0 2006-11-02 12:15:57.132
!MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists:
!SUBENTRY 1 org.eclipse.osgi 2 0 2006-11-02 12:15:57.132
!MESSAGE Bundle update@plugins/org.eclipse.swt.gtk.linux.x86_3.3.0.v3309.jar [23] was not resolved.
!SUBENTRY 2 org.eclipse.swt.gtk.linux.x86 2 0 2006-11-02 12:15:57.132
!MESSAGE Platform filter did not match: (& (osgi.ws=gtk) (osgi.os=linux) (osgi.arch=x86))
!SUBENTRY 2 org.eclipse.swt.gtk.linux.x86 2 0 2006-11-02 12:15:57.132
!MESSAGE Missing Constraint: Fragment-Host: org.eclipse.swt; bundle-version="[3.0.0,4.0.0)"

Look at these lines:
BootLoader constants: OS=linux, ARCH=x86, WS=motif, NL=en_CA
..
..
..
!MESSAGE Platform filter did not match: (& (osgi.ws=gtk) (osgi.os=linux) (osgi.arch=x86))


So what happens is that for any reason java wants to start with the "motif" window system but the package is exported with gtk. So I tried to add to the
"java -Dosgi.configuration.area=... startup.jar -console -noExit" command "-ws gtk" and it started perfectly.

So I guess that with Java Web Start the same does happen. When I look at the log file of the Java Web Start launch I can see the same in the header, it launches as "motif" but should launch as "gtk". The Eclipse help says that you should add this to your main jnlp to solve this issue:
  <resources os="Linux"/>
        <property name="osgi.ws" value="gtk"/>
  </resources>

I did that but it still launches as "motif".
So here is my main jnlp file again:
<?xml version="1.0" encoding="UTF-8"?>
<jnlp 
    spec="1.0+" 
    codebase="file:///home/prutsch/bin/helloworld" 
    href="hello.jnlp"> <!-- URL to the site containing the jnlp application. It should match the value used on  export. Href, the name of this file -->
  <information>
    <!-- user readable name of the application -->
    <title> Hello Web Start </title>  
    <!-- vendor name -->
    <vendor>Hello</vendor>
    <!-- vendor homepage --> 
    <homepage href="http://www.helloworld.com" /> 
    <!-- product description -->
    <description>GUI Aplication to test Java Web Start</description> 
    <icon kind="splash" href="splash.gif"/>
  </information>
 
  <!--request all permissions from the application. This does not change-->
  <security>
    <all-permissions/>
  </security>
 
  <!-- The name of the main class to execute. This does not change-->
  <application-desc main-class="org.eclipse.core.launcher.WebStartMain">
    <argument>-nosplash</argument>
  </application-desc>
 
  <resources>
    <!-- Reference to the startup.jar. This does not change -->
    <jar href="startup.jar"/>
 
    <!-- Reference to all the plugins and features constituting the application -->
    <!-- Here we are referring to the wrapper feature since it transitively refers to all the other plug-ins  necessary -->
    <extension 
        name="Hello Feature"
        href="features/test.rcphellowebstart.feature_1.0.0.jnlp"/>
    <!-- Information usually specified in the config.ini -->
    <property 
        name="osgi.instance.area" 
        value="/tmp/workspace"/>
    <property 
        name="osgi.configuration.area" 
        value="/tmp/config"/>
        
    <!-- The id of the product to run, like found in the overview page of the product editor-->
    <property 
        name="eclipse.product" 
        value="test.rcphellowebstart.product"/> 
  </resources>

  <!-- Indicate on a platform basis which JRE to use --> 
  <resources os="Mac">
    <j2se version="1.5+" java-vm-args="-XstartOnFirstThread"/>
  </resources>
  <resources os="Windows">
    <j2se version="1.5+"/>
  </resources>
  <resources os="Linux">
    <j2se version="1.5+"/>
  </resources>


  <!-- start as gtk --> 
  <resources os="Linux"/>
        <property name="osgi.ws" value="gtk"/>
  </resources>
</jnlp>



OK, so far my results. Java Web Start still doesn't work but I have the feeling that I'm almost there.(Hopefully)

Pyoeter
Re: RCP + Java Web Start, Application doesn't launch [message #457585 is a reply to message #457579] Thu, 02 November 2006 22:15 Go to previous messageGo to next message
Alex Blewitt is currently offline Alex BlewittFriend
Messages: 946
Registered: July 2009
Senior Member
Make sure you clean our your workspace/config if you've upgraded to Eclipse 3.3.

As for the starting with motif/gtk, that could be the case. I'm not sure why it wouldn't figure out the platform filter, though. What does os.name and os.arch report? Those are used to calculate the values that Eclipse uses to startup.

Lastly, I suspect that the JNLP file might be being cached sometimes by Java WebStart. You could try finding where that is and then cleaning the cache (as well as previously downloaded bundles).

I think that Linux defaults to motif, unless you specify otherwise.

You might also be able to put -noExit on the command for JNLP, and -console 1234, and then you can telnet to port 1234 after the JNLP starts to gain access to the console. That way, you'll find the state exactly as the Java WebStart finds it.

Alex.
Re: RCP + Java Web Start, Application doesn't launch [message #457704 is a reply to message #457585] Fri, 03 November 2006 22:46 Go to previous messageGo to next message
Peter Rutsch is currently offline Peter RutschFriend
Messages: 19
Registered: July 2009
Junior Member
Hi,

so here are the latest news.
I put the hello world application on a web server and opened the jnlp file on a windows machine. No problems, everything worked fine.Then I started it on a Mac. The application launched, but didn't respond to user inputs, e.g. you couldn't close it anymore. This is probably the same problem as in this bug report: https://bugs.eclipse.org/bugs/show_bug.cgi?id=63306

I also tried your suggestion to telnet into the application, but that didn't work. I added this to the jnlp file:
<!-- The name of the main class to execute. This does not change-->
  <application-desc main-class="org.eclipse.core.launcher.WebStartMain">
    <argument>-nosplash</argument>
    <argument>-console 1234</argument>
    <argument>-noExit</argument>
    <argument>-ws gtk</argument>
  </application-desc>

You see I tried some other things as well, e.g. I tried to pass -ws gtk to the command line. I just wanted to see what happens, because this way I was able to launch the feature. But no success.

I tried things like that:
<!-- Indicate on a platform basis which JRE to use -->
  <resources os="Mac">
    <j2se version="1.5+" java-vm-args="-XstartOnFirstThread"/>
  </resources>
  <resources os="Linux">
    <j2se version="1.5+" java-vm-args="-ws gtk"/>
  </resources>

No success.

I looked again in the cache folder of jws, and actually I didn't look right the first time when I checked the folder. My machine didn't download the org.eclipse.swt.gtk.linux.x86_3.3.0.v3309.jar. I wondered why. Then I checked like you suggested what java returns when you check the system properties for os.name and os.arch. It is "Linux" and "i386", so I added this to the jnlp file where all the OS connections are specified:
<resources os="Linux" arch="i386">
        <jar href="plugins/org.eclipse.swt.gtk.linux.x86_3.3.0.v3309.jar"/>
</resources>

Then I checked the folder again, and this time it downloaded it. But still no web start. :-(

Then I changed it to motif:
<resources os="Linux" arch="i386">
        <jar href="plugins/org.eclipse.swt.gtk.linux.x86_3.3.0.v3309.jar"/>
</resources>
 

and got this error message:
!SESSION 2006-11-03 17:42:10.986 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.5.0_06
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=motif, NL=en_CA
Framework arguments:  -console 1234
Command-line arguments:  -console 1234

!ENTRY org.eclipse.osgi 4 0 2006-11-03 17:42:13.070
!MESSAGE Application error
!STACK 1
java.lang.UnsatisfiedLinkError: /tmp/config/org.eclipse.osgi/bundles/27/1/.cp/libswt-motif-3309.so: libXm.so.2: cannot open shared object file: No such file or directory
    at java.lang.ClassLoader$NativeLibrary.load(Native Method)
    at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1751)
    at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1660)
    at java.lang.Runtime.loadLibrary0(Runtime.java:822)
    at java.lang.System.loadLibrary(System.java:992)
    at org.eclipse.swt.internal.Library.loadLibrary(Library.java:123)
    at org.eclipse.swt.internal.motif.OS.<clinit>(OS.java:18)
    at org.eclipse.swt.graphics.Device.<clinit>(Device.java:115)
    at org.eclipse.ui.internal.Workbench.createDisplay(Workbench.java:433)
    at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:161)
    at test.rcphellowebstart.Application.run(Application.java:16)
    at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:104)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:74)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:348)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:165)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.eclipse.core.launcher.Main.invokeFramework(Main.java:341)
    at org.eclipse.core.launcher.Main.basicRun(Main.java:285)
    at org.eclipse.core.launcher.WebStartMain.basicRun(WebStartMain.java:59)
    at org.eclipse.core.launcher.Main.run(Main.java:987)
    at org.eclipse.core.launcher.WebStartMain.main(WebStartMain.java:40)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.sun.javaws.Launcher.executeApplication(Launcher.java:1154)
    at com.sun.javaws.Launcher.executeMainClass(Launcher.java:1101)
    at com.sun.javaws.Launcher.continueLaunch(Launcher.java:944)
    at com.sun.javaws.Launcher.handleApplicationDesc(Launcher.java:515)
    at com.sun.javaws.Launcher.handleLaunchFile(Launcher.java:218)
    at com.sun.javaws.Launcher.run(Launcher.java:165)
    at java.lang.Thread.run(Thread.java:595)



That's it so far.
Re: RCP + Java Web Start, Application doesn't launch [message #457706 is a reply to message #457704] Fri, 03 November 2006 23:08 Go to previous messageGo to next message
Alex Blewitt is currently offline Alex BlewittFriend
Messages: 946
Registered: July 2009
Senior Member
Couple of things:

When specifying arguments, you have to put each on a separate line:


<argument>-ws</argument>
<argument>gtk</argument>
<argument>-console</argument>
<argument>1234</argument>
[/xml]

I'll also assume that you meant to type 'org.eclipse.swt.motif' instead of '.swt.gtk' the second time around :-)

I believe that JNLP with SWT on the Mac currently doesn't work. I know there's ongoing bug reports about this but think that the next fix is coming out of Apple to make it work.

The library suggests that the SWT fragment was found (and loaded) but then couldn't find motif installed on linux. Presumably, if you don't have motif, then that might be why. Also, the library path (LD_LIBRARY_PATH) would need to be set up to load the libraries from the right locations. Chances are, they should be set up already ...
Re: RCP + Java Web Start, Application doesn't launch [message #457709 is a reply to message #457706] Sat, 04 November 2006 00:51 Go to previous messageGo to next message
Peter Rutsch is currently offline Peter RutschFriend
Messages: 19
Registered: July 2009
Junior Member
Ta-ta!!! OK my hello web start world runs now for the first time.
I put in the arguments like you said, for each a line.

So the problem was that java didn't launch with gtk. BUT now that I fixed that and added the lines it doesn't start on windows anymore. I wonder why it doesn't respect these lines in the jnlp file:

<resources os="Linux"/>
      <property name="osgi.ws" value="gtk"/>
</resources>

I also tried this, just in case:
<resources os="Linux" arch="i386"/>
      <property name="osgi.ws" value="gtk"/>
</resources>

At least it started, I'm already happy. Thank you very much for your support.

So you think the support for Mac should only be a matter of time? In the bug report it sounded as if they have some serious problems.

<u>"We have some core problems with SWT and AWT
running together that I need to address first. Once that happens I can look at
having the SWT start after the AWT which is the root problem here."</u>
Re: RCP + Java Web Start, Application doesn't launch [message #457711 is a reply to message #457709] Sat, 04 November 2006 08:50 Go to previous messageGo to next message
Alex Blewitt is currently offline Alex BlewittFriend
Messages: 946
Registered: July 2009
Senior Member
Well, of course you can't say -ws gtk on a Windows box -- that would prevent it from running on a bunch of places! You might have to have a separate JNLP for Linux. I'm not really sure why the resource didn't work. You could try the following:

Move the -ws arg to a osgi.ws property (but on all platforms). See if it launches on Linux. Then, once you've tested this, you could try and find out whether putting it in a Linux resource block (maybe it's the capital letter in Linux? Did you try linux?). That should fix that problem.

As for the Mac/WebStart thing; you've found the bug, Cc yourself on it. What's happening is that the WebStart is starting up the AWT thread, and the AWT thread is getting in the way of the SWT thread running. What they're having to do is find a way of getting AWT to shut down prior to SWT coming up after the load, or use a different process to launch the downloaded WebStart. However, since those changes require bugs to be fixed in the JavaVM, it's really a matter of waiting for Apple's engineers to solve the problem and make a new version of the VM with the fixes. (They've done this already; the -XstartOnFirstThread argument is a fix to support SWT on Apple; it's just that WebStart brings up the AWT thread before this argument gets processed at the moment.) Stay tuned ...
Re: RCP + Java Web Start, Application doesn't launch [message #457804 is a reply to message #457711] Tue, 07 November 2006 21:48 Go to previous messageGo to next message
Peter Rutsch is currently offline Peter RutschFriend
Messages: 19
Registered: July 2009
Junior Member
Ok, I tried your suggestion and added the following to my JNLP file:
  <resources os="linux"/>
        <property name="osgi.ws" value="gtk"/>
  </resources>
  <resources os="Linux"/>
        <property name="osgi.ws" value="gtk"/>
  </resources>
  <resources os="Windows"/>
        <property name="osgi.ws" value="gtk"/>
  </resources>
  <resources os="windows"/>
        <property name="osgi.ws" value="gtk"/>
  </resources>
  <resources os="Mac"/>
        <property name="osgi.ws" value="gtk"/>
  </resources>
  <resources os="mac"/>
        <property name="osgi.ws" value="gtk"/>
  </resources>

Just to cover everything. It still doesn't work. So what we are going to do now, as a temporary solution, is to provide two jnlp files for the different platforms.

I wonder if I should post that as a bug either to the Web Start bugtracker or the Eclipse RCP bugtracker with the information of my operating system, java version, etc.

Thank you for all your time and effort. You really helped to find the source of the problem and "solve" it.

Peter
Re: RCP + Java Web Start, Application doesn't launch [message #457805 is a reply to message #457804] Tue, 07 November 2006 22:06 Go to previous messageGo to next message
Alex Blewitt is currently offline Alex BlewittFriend
Messages: 946
Registered: July 2009
Senior Member
Try it without a per-OS thing e.g.


<resources>
<property name="osgi.ws" value="gtk"/>
</resources>
[/xml]

See if that works. Then, once you know, you can try to restrict it to a per-OS setting. If the -ws works, but the osgi.ws doesn't, then file a bug at http://bugs.eclipse.org

Alex.
Re: RCP + Java Web Start, Application doesn't launch [message #457806 is a reply to message #457805] Tue, 07 November 2006 22:24 Go to previous messageGo to next message
Peter Rutsch is currently offline Peter RutschFriend
Messages: 19
Registered: July 2009
Junior Member
Ok, when I add the lines at the beginning of the Resource block the application starts. I can also write something like:
<resources arch="i386">
<property name="osgi.ws" value="gtk"/>
</resources> 


And it starts. But it doesn't start if I have any OS mappings in the file before this block. Even if they are Windows or Mac mappings.
I double checked that System.out.println(System.getProperty("os.name")), it prints "Linux". But it doesn't work work with a Linux mapping.
Re: RCP + Java Web Start, Application doesn't launch [message #457812 is a reply to message #457806] Wed, 08 November 2006 08:57 Go to previous messageGo to next message
Alex Blewitt is currently offline Alex BlewittFriend
Messages: 946
Registered: July 2009
Senior Member
I think you can only have one 'resources' block for each os/arch combination. So:


<resources>
...
</resources>
<resources>
...
</resources>
[/xml]

won't work, because it assumes you've got exactly one 'resources' block. Perhaps that's your problem? Also, it will probably be case-insensitive, so specifying the resources with 'mac' and 'Mac' may be causing problems.

By the way, os.name on Mac is "Mac OS X".

Alex.
Re: RCP + Java Web Start, Application doesn't launch [message #458073 is a reply to message #457812] Mon, 13 November 2006 16:26 Go to previous messageGo to next message
Peter Rutsch is currently offline Peter RutschFriend
Messages: 19
Registered: July 2009
Junior Member
The last issue is solved now too! It's so embarrassing that I even shouldn't tell it here. The problem was that the Ressources block used an empty tag so it never read the child element:
<resources os="Linux"/>
        <property name="osgi.ws" value="gtk"/>
</resources>

I must have copy/pasted it from somewhere and didn't realize it.

Problem solved. Thank you Alex.

Pyoeter
Re: RCP + Java Web Start, Application doesn't launch [message #458214 is a reply to message #457709] Wed, 15 November 2006 18:34 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: linux.kaiho.de

Hi Pyoeter!

I've the same problem that you described in http://eclipsezone.com/eclipse/forums/t83652.html#92058187:

org.osgi.framework.BundleException: The activator org.eclipse.ui.internal.WorkbenchPlugin for bundle org.eclipse.ui.workbench is invalid
....
Caused by: java.lang.NoClassDefFoundError: org/eclipse/swt/SWTError

The error occurs although I've added ...property name="osgi.ws" value="gtk"... in the JNLP-file and that seems to work:

BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=de_DE

You said "So the problem was that java didn't launch with gtk." and this sounds as I have to say java/javaws to start with gtk (besides the osgi.ws-thing). How do I accomplish that? (My System is SUSE 10.0).

Thanks for your help!
Kai
Re: RCP + Java Web Start, Application doesn't launch [message #458215 is a reply to message #458214] Wed, 15 November 2006 18:56 Go to previous messageGo to next message
Peter Rutsch is currently offline Peter RutschFriend
Messages: 19
Registered: July 2009
Junior Member
Hi Kai,

try to add this to the jnlp file that specifies the paths to the swt jars for the different OS + Architecture combinations:
<resources os="Linux" arch="i386">
		<jar href="plugins/org.eclipse.swt.gtk.linux.x86_3.3.0.v3309.jar"/>
</resources>

Suse 10 seems to have a combination that isn't mentioned in the example in the Eclipse help. This solved the problem for me.
Re: RCP + Java Web Start, Application doesn't launch [message #458311 is a reply to message #458215] Thu, 16 November 2006 22:04 Go to previous messageGo to next message
Peter Rutsch is currently offline Peter RutschFriend
Messages: 19
Registered: July 2009
Junior Member
I know now why I had the typo in the ressources block. I copied it out of the Eclipse help and there it was written with an empty tag:
<resources os="Linux"/>
        <property name="osgi.ws" value="gtk"/>
</resources>

I opened a bug report, which was alredy fixed:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=164875

And another bug report for the missing ressource mapping for Suse 10.0:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=164888
Re: RCP + Java Web Start, Application doesn't launch [message #458312 is a reply to message #458311] Thu, 16 November 2006 22:22 Go to previous messageGo to next message
Alex Blewitt is currently offline Alex BlewittFriend
Messages: 946
Registered: July 2009
Senior Member
That would explain it ... someone else had that problem recently :-)

Alex.
Re: RCP + Java Web Start, Application doesn't launch [message #458341 is a reply to message #458215] Fri, 17 November 2006 20:00 Go to previous message
Kai is currently offline KaiFriend
Messages: 12
Registered: July 2009
Junior Member
Hi Pyoeter,

referencing the swt-jar with arch="i386" instead of arch="x86" works for me too. Thank you very much! I wouldn't have been able to fix it myself. Thanks for the bug report. I hope that others will not spend as much time as we on that bug. ;-)

Kai
Previous Topic:order of actions defined by means of actionSet
Next Topic:ActionSets
Goto Forum:
  


Current Time: Tue Apr 23 07:01:21 GMT 2024

Powered by FUDForum. Page generated in 0.06361 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top