Skip to Content
Last modified by David Avendasora on 2008/07/01 16:52
From version 33.1
edited by David Avendasora
on 2008/06/26 10:29
Change comment: There is no comment for this version
To version 36.1
edited by David Avendasora
on 2008/07/01 16:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,6 +1,6 @@
1 1  This tutorial will help you create a single Eclipse/WOLips project that contains both the client- and server-side classes of a WebObjects Java Client project, build both applications and then launch them both.
2 2  
3 -You can also create a Java Client application using two separate Eclipse WebObjects projects. One for the server, and one for the client. This will make the separation between client and server much more obvious, but then you will have two Eclipse projects to maintain.
3 +You can also create a Java Client application using two separate Eclipse projects. One for the server (a WOLips project), and one for the client (most likely a plain Java project). This will make the separation between client and server much more obvious, but then you will have two Eclipse projects to maintain. The approach described in this tutorial is most appropriate for WebStart based client app distribution.
4 4  
5 5  1. Create a new WebObjects Application
6 6  [[image:Picture 9.png]]
... ... @@ -55,6 +55,7 @@
55 55  {{note title="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.{{/note}}
56 56  
57 57  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.
58 +If you don't specify a client class name for each entity, then WebObjects will automatically use EOGenericRecord as it's class. Once you want to start specifying client-side logic including default values and such, you will need to add the Client Class Name to the Entity in the EOModel, and then setup a new .eogen file in eclipse to generate the client-side classes.
58 58  1. Add the following frameworks to the project build path:
59 59  JavaDirectToWeb
60 60  JavaDTWGeneration
... ... @@ -114,7 +114,7 @@
114 114  [[image:Picture 13.png]]
115 115  1. Select your.app.Application as the Application class
116 116  [[image:Picture 14.png]]
117 -1. If you want to actually deploy this application, then you will also need to [[modify the build.xml file>>Java Client-Building]].
118 +1. If you want to actually deploy this application, then you will also need to [[modify the build.xml file>>Java Client-WebStart Distribution Building]].
118 118  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:
119 119  [[image:Picture 15.png]]
120 120  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>>http://web.mac.com/flor385/JBND/]]