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

Summary

Details

Page properties
Content
... ... @@ -55,7 +55,6 @@
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.
59 59  1. Add the following frameworks to the project build path:
60 60  JavaDirectToWeb
61 61  JavaDTWGeneration