Skip to Content

Changes for page EOF-Using EOF-EOGenerator

Last modified by Pascal Robert on 2012/01/21 22:03
From version 21.1
edited by Pascal Robert
on 2007/12/21 20:55
Change comment: There is no comment for this version
To version 22.1
edited by Pascal Robert
on 2007/09/03 13:44
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -5,12 +5,6 @@
5 5  
6 6  If you've ever used EOModeler's Java source code generator, you know how much of a pain it can be when you make changes to your model objects and have to merge changes in later. One solution for this is to use [[EOGenerator>>http://www.rubicode.com/Software/EOGenerator/]], an application developed by Rubicode Software, which uses the Generation Gap pattern to create your Java files from your EOModels. EOGenerator produces TWO java files for each Entity rather than one. Take the example of a Person entity. The first java file is Person.java, which contains all of the autogenerated methods. The second java file is Person.java, and Person extends Person. The second file is where you place all of your customizations. Any time your model changes, only your Xxx.java files are updated, and your customizations are left untouched. Additionally, EOGenerator allows for the creation of extensive custom templates for your files, which provides the ability to place convenience methods in your Xxx.java files.
7 7  
8 -{{warning}}
9 -
10 -EOGenerator don't work on Mac OS X 10.5.  You either have to use [JavaEOGenerator|http://developer.apple.com/samplecode/JavaEOGenerator/] or [Velocity EOGenerator|WOL:Velocity EOGenerator (Veogen)].
11 -
12 -{{/warning}}
13 -
14 14  == Advantages ==
15 15  
16 16  There are several advantages to using EOGenerator over EOModeler's default Java file generation and merging with FileMerge.