Skip to Content
Last modified by David Avendasora on 2009/01/22 11:26
From version 18.1
edited by David Avendasora
on 2009/01/22 08:31
Change comment: There is no comment for this version
To version 19.1
edited by David Avendasora
on 2009/01/22 10:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -14,8 +14,36 @@
14 14  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.
15 15  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.
16 16  
17 -1. 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. 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.
17 +1. 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.
18 18  
19 +{{noformat}}
20 +
21 +# ApplicationClass == com.webobjects.eoapplication.client.EOClientApplicationSupport
22 +# JDB == jdb
23 +# JDBOptions ==
24 +# JVM == java
25 +# JVMOptions ==
26 +APPROOT/WebServerResources/Java/MyApp.jar
27 +/System/Library/Frameworks/JavaFoundation.framework/WebServerResources/Java/JavaFoundation.jar
28 +WOROOT/Library/Frameworks/JavaEOControl.framework/WebServerResources/Java/JavaEOControl.jar
29 +WOROOT/Library/Frameworks/JavaXML.framework/WebServerResources/Java/JavaXML.jar
30 +WOROOT/Library/Frameworks/JavaDirectToWeb.framework/WebServerResources/Java/JavaDirectToWeb.jar
31 +WOROOT/Library/Frameworks/JavaEOApplication.framework/WebServerResources/Java/JavaEOApplication.jar
32 +WOROOT/Library/Frameworks/JavaEODistribution.framework/WebServerResources/Java/JavaEODistribution.jar
33 +WOROOT/Library/Frameworks/JavaEOGeneration.framework/WebServerResources/Java/JavaEOGeneration.jar
34 +WOROOT/Library/Frameworks/JavaEOInterface.framework/WebServerResources/Java/JavaEOInterface.jar
35 +WOROOT/Library/Frameworks/JavaEOInterfaceSwing.framework/WebServerResources/Java/JavaEOInterfaceSwing.jar
36 +WOROOT/Library/Frameworks/JavaEORuleSystem.framework/WebServerResources/Java/JavaEORuleSystem.jar
37 +WOROOT/Library/Frameworks/JavaWOJSPServlet.framework/WebServerResources/Java/JavaWOJSPServlet_client.jar
38 +HOMEROOT/Library/Java
39 +LOCALROOT/Library/Java
40 +WOROOT/Library/Java
41 +/Network/Library/Java
42 +WOROOT/Library/Frameworks/JavaVM.framework/Classes/classes.jar
43 +WOROOT/Library/Frameworks/JavaVM.framework/Classes/ui.jar
44 +
45 +{{/noformat}}
46 +
19 19  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>>Java Client-WebStart Incremental Build]] page.
20 20  
21 21  If everything is setup correctly, when you run your project in Eclipse/WOLips you will see the following in the console: