Skip to Content

Java Client and Direct To Java Client Example Project using WebStart

Version 34.1 by David Avendasora on 2008/06/25 10:18
Warning: For security reasons, the document is displayed in restricted mode as it is not the current version. There may be differences and errors due to this.

This tutorial will help you get a new Java Client or Direct To Java Client Application setup in Eclipse/WOLips and get it building properly.

  1. Create a new WebObjects Application
    Picture 9.png
  2. Name it "WebStartJNLPTest" in Eclipse with a package of "your.app" The [note] macro is a standalone macro and it cannot be used inline. Click on this message for details.
  3. Modify the Main.html by adding:
Main.html Changes
<WEBOBJECT NAME=JavaClientLink>click here</WEBOBJECT>
  1. Modify the Main.wod file by adding:
Main.wod Changes
JavaClientLink: WOHyperlink {
    href = javaClientLink;
}
  1. Modify the Main.java file by adding:
Main.java Changes

public String javaClientLink() {
return WOJavaClientComponent.webStartActionURL(context(), "JavaClient");
}
  1. Create a WOComponent named "JavaClient".
    Picture 11.pngPicture 10.png
    This WOComponent will be what passes the specifics about your client-side application to WebObjects. 
  2. Modify the JavaClient.html replacing the contents with:
JavaClient.html Contents
<WEBOBJECT NAME=JavaClientComponent></WEBOBJECT>
  1. Paste the following as the contents of the JavaClient.wod file. Feel free to change the applicationName, applicationDescription and vendor parameters to anything you wish.
JavaClient.wod Contents

JavaClientComponent: WOJavaClientComponent {
    applicationClassName = "com.webobjects.eogeneration.EODynamicApplication";
    applicationName = "D2JC WebStart Test";
    applicationDescription = "D2JC WebStart Test";
    downloadClientClasses = "noDownloadClientClasses";
    vendor = "My Company";
}
Warning

Note!

If you are not creating a Direct To Java Client (D2JC) application, then you will need to replace the applicationClassName parameter (com.webobjects.eogeneration.EODynamicApplication) with the name of your client-side application class. Your non-D2JC client-side Application class *must* subclass EOApplication.

  1. If you didn't add an EOModel file to the project when you created it, do it now. Drop any existing EOModel in the Resources directory, or create one from scratch.
  2. Add the following frameworks to the project build path:
    JavaDirectToWeb
    JavaDTWGeneration
    JavaEOApplication
    JavaEOControl
    JavaEODistribution
    JavaEOGeneration
    JavaEOInterface
    JavaEOInterfaceSwing
    JavaEOProject
    JavaEORuleSystem
    JavaFoundation
    JavaJDBCAdaptor
    JavaWebObjects
    JavaWOExtensions
Warning

Note!

 If you are not creating a D2JC application, then you won't need all of these, but they won't hurt anything either.

  1. Create a ClasspathClient.txt file in the root of the project and paste the following as contents:The [note] macro is a standalone macro and it cannot be used inline. Click on this message for details.
ClasspathClient.txt File

# ApplicationClass == com.webobjects.eoapplication.client.EOClientApplicationSupport
# JDB              == jdb
# JDBOptions       ==
# JVM              == java
# JVMOptions       ==
APPROOT/WebServerResources/Java/WebStartJNLPTest.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

This file is only required by the application when it is being launched from within Eclipse.

  1. Create a Java Client Incremental Builder by following the instructions. This file is needed to make up for the lack of Java Client application building by the WOLips Incremental Builder. It also copies the client launch scripts into the project so that the application will auto-launch when you run it from within Eclipse. 
  2. If you did not setup the Java Client Incremental Builder, then right-click on the javaclientbuild.xml file and select "Run As -> Ant Build"
    Picture 12.png
  3. Right-click on the project and select "Run As -> WebObjects Application"
    Picture 13.png
  4. Select your.app.Application as the Application class
    Picture 14.png
  5. If you want to actually deploy this application, then you will also need to modify the build.xml file.
    This is it. WebStart should automatically download your client application and launch it. If you are creating a D2JC application and did not put an EOModel file in the Resources directory of your project, then you'll see something like this:
    Picture 15.png
    If you don't want a D2JC application, then you are on your own for creating the user interface for it. Your client-side application can be a command-line or GUI application. If you want a Swing GUI, then I highly recommend Florijan Stamenkovic's JBND Framework