Okay, fist thing I'd say is don't use XCodes built-in modeler. But since you didn't ask about that I won't go into all the details. 1) Open the model in EOModeler and generate them using it's function under the "Property" menu: "Generate Java files..." and "Generate Client Java files..." Pro: Simple Con: if you make changes to the .java files, then make a change to the EOModel and re-generate the files, your changes will be overwritten. 2) Use EOGenerator http://www.rubicode.com/Software/EOGenerator/ Pro: MUCH, MUCH more powerful and keeps you from overwriting changes to .java files. Con: More complicated, command-line UI If you are doing anything more than experimenting, use EOGenerator as it greatly reduces the amount of work you will do long-term, especially if you are still revising your EOModel. Most everyone uses it in conjunction with EOModeler. Dave On May 10, 2006, at 5:33 AM, Philippe Lafoucrière wrote: Hello, |
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
