Community
Participate
Working Groups
Build ID: N20060118-1600 Steps To Reproduce: I am building an RCP application. When I attempt to launch the application through Java Web Start, the splash screen does not appear when the application begins launching. There is a delay of about 30 seconds between the time the application starts launching and the time when the Splash Screen starts running. Once the splash screen is running, it runs for about another 30 seconds. It takes about a minute for the whole application to launch. I would like the splash screen to open more quickly. More information:
Any ideas Andrew?
Java Web start apparently has its own splash screen mechanism. I assume this is refering to that splash mechanism since the eclipse splash screen doesn't work in java web start. I don't know anything about that mechanism. To do our normal splash in webstart, the launcher fragment containing the shared library would be in jar form if it is there at all. WebStartMain would need to extract the shared library to disk before we could do a webstart eclipse splash screen. I don't know if this would be any faster than the normal webstart splash.
One thing that possibly helps here (as I also fight timing issues) Set an osgi.install.area. To whatever. When activating osgi.debug and the java console I saw (on my webstart rcp app) that it is using a remote (!!) install area by default --- thus waiting for timeout or 404 in an hopeless quest to find a config.ini. This can take some time. Sadly setting anything with @user.home doesn't work because @user.home is NOT RESOLVED for osgi.install.area in Java Web Start, but then it uses a local url that fails much faster :-) There should be found some mechanism to launch WITHOUT searching for the config.ini (thus defaulting)! Tested with Eclipse 3.3 and Java 6 Update 2.
Even one more: In Java6 all the JAR files CAN be found (thinking of faster OSGi start) http://java.sun.com/javase/6/docs/technotes/guides/javaws/enhancements6.html see "Jar Indexing is fully supported now" It would be great to open our "own" splash as fast as possible (after webstart splash) for progress, etc...
Is there any progress on this front ? We have an interactive login - splash screen with 3.3.1.1. Everything works fine when we run the product as standalone. But when we try using webstart, the splash handler is not initialized, just ignored. We use the new equinox webstart launcher <application-desc main-class="org.eclipse.equinox.launcher.WebStartMain"> <argument>-showSplash</argument> </application-desc> (btw the documentation on the website is wrong regarding the package for this launcher http://help.eclipse.org/help33/index.jsp?topic=/org.eclipse.platform.doc.isv/guide/java_web_start.htm ) We are kind of stuck now... I ve seen issues around the webstart launcher recently - in case this is related (Bug 198462)
Splash screen from webstart works in 3.4 *** This bug has been marked as a duplicate of bug 209694 ***
