Launching your WebStart-based client-side application from within Eclipse/WOLips
There are two key files that help with launching your WebStart-based Java Client application from within WOLips.
- The Client Launch Script. This script allows Eclipse to automatically lanuch the client-side application for you when you run the application from within Eclipse. Without this scrip you will get the following message in the console.
Apple includes this script with WebObjects (/Library/Application Support/Apple/Developer Tools/WebObjects Support/UnixLaunch.sh). There is also a Windows .CMD file that serves the same purpose on Windows. Its implementation should be similar but I have not tested it.
If this occurs, the application will revert to launching the regular way by opening a web browser and loading the Main component, which means that you will still be able to launch your client-side application by clicking on the link for it in your web browser, it's just not as convenient as having the application launch immediately upon running.
- The Client-Side Classpath File (ClasspathClient.txt). This file defines the classpath for all the .jars that need to be available for the client-side application to download from the server. Right now this file is not automatically created by the build process so you have to manually maintain it. If this file is not present or if there are errors in it, you will likely not be able to launch your client-side application using the Launch Script.
Both of these files need to be copied into your app's build directory as part of the incremental build process. This is already documented in the Java Client-WebStart Incremental Build page.
If everything is setup correctly, when you run your project in Eclipse/WOLips you will see the following in the console:
Copy-Pasting this line into Terminal.app will allow you to launch the client-side application, and any errors generated by the launch will show up in the terminal.