Child pages
  • Java Client-Additional Files and Settings

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. 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 instead of you needing to launch it manually using the normal Java WebStart process. Without this scrip you will get the following informational message in the console.
    No Format
    Unable to locate client launch script in your application, 
    using the Auto Open In Browser feature instead of the Auto Open Client Application feature.
    
    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 (which launches the app using Java WebStart), it's just not as convenient as having the application launch immediately upon running.
    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.
  2. The Client-Side Classpath File (ClasspathClient.txt). This file defines the classpath for the client-side application. This is different than the classpath information that the server-side portion of a Java Client application uses. It appears that this file is only used by the Launch Script and not used when launching the client-side application using WebStart. 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. Here is a bare-bones file. You'll need to add any additional Frameworks you've added to the project build path.
    No Format
    # ApplicationClass == com.webobjects.eoapplication.client.EOClientApplicationSupport
    # JDB              == jdb
    # JDBOptions       == 
    # JVM              == java
    # JVMOptions       == 
    APPROOT/WebServerResources/Java/MyApp.jar
    LOCALROOT/Library/Frameworks/MyFramework.framework/WebServerResources/Java/MyFramework.jar
    /System/Library/Frameworks/JavaFoundation.framework/WebServerResources/Java/JavaFoundation.jar
    WOROOT/Library/Frameworks/JavaEOControl.framework/WebServerResources/Java/JavaEOControl.jar
    WOROOT/Library/Frameworks/JavaXML.framework/WebServerResources/Java/JavaXML.jar
    WOROOT/Library/Frameworks/JavaDirectToWeb.framework/WebServerResources/Java/JavaDirectToWeb.jar
    WOROOT/Library/Frameworks/JavaEOApplication.framework/WebServerResources/Java/JavaEOApplication.jar
    WOROOT/Library/Frameworks/JavaEODistribution.framework/WebServerResources/Java/JavaEODistribution.jar
    WOROOT/Library/Frameworks/JavaEOGeneration.framework/WebServerResources/Java/JavaEOGeneration.jar
    WOROOT/Library/Frameworks/JavaEOInterface.framework/WebServerResources/Java/JavaEOInterface.jar
    WOROOT/Library/Frameworks/JavaEOInterfaceSwing.framework/WebServerResources/Java/JavaEOInterfaceSwing.jar
    WOROOT/Library/Frameworks/JavaEORuleSystem.framework/WebServerResources/Java/JavaEORuleSystem.jar
    WOROOT/Library/Frameworks/JavaWOJSPServlet.framework/WebServerResources/Java/JavaWOJSPServlet_client.jar
    HOMEROOT/Library/Java
    LOCALROOT/Library/Java
    WOROOT/Library/Java
    /Network/Library/Java
    WOROOT/Library/Frameworks/JavaVM.framework/Classes/classes.jar
    WOROOT/Library/Frameworks/JavaVM.framework/Classes/ui.jar
    

...