This is a basic guide to getting the Velocity Generator to work under Leopard, using Eclipse 188.8.131.52 and WOLips 3.3.4669, later versions should work. The guide is basic in that it should work the way it's detailed below, it doesn't represent the only way, nor probably an optimized way to work with Velocity Generator.
History and Context
(from Pierce T Wetter III)
EOModeler had built in code generation, which always sucked, because it didn't use the Generation Gap Pattern. It used some kind of Apple-specific template format.
EOGenerator, written in objc, relied on an objc-EOF framework to parse the model. That's broken in Mac OS 10.5, (WO 5.4), even if you have the 5.3 frameworks installed, because the Java-objc bridge it uses is not available on 10.5. It uses MiscMerge templates, an open source objc library.
JavaEOGenerator is an Apple replacement that uses WO style templates (.html, .wod, etc.), which means it's actually written as a .woa. It uses the WO code to parse the model. The advantage of it is that if Apple changes the model file format, presumably they might change JavaEOGenerator. The disadvantage is that you have to rewrite your templates anyways.
What people are calling VelocityGenerator is built into WOLips, and uses the code from EntityModeler inside WOLips to parse the model. Given that Apple is funding EntityModeler these days, presumably it will be inherently compatible with any/all .eomodel files going forward. It uses a template library in Velocity format, Velocity being an open source Java library. It's main advantage is that it's built into WOLips, so there's nothing else to install, and it has some useful built-in defaults (like looking in a templates folder for the templates).
My decision: After considering the above, I went with the Velocity templates. They were built in, the .eogen default was to use that anyways, so I'll have zero-config issues with the other team members, and Mike Shrag's public much-more-capable template examples were in that format anyways.
There are two ways: create eclipse-wide settings, or create settings per project.
eclipse-wide settings for EOGeneration
1. Download the templates that Mike Schrag made from http://webobjects.mdimension.com/wolips/EOGenerator/Velocity%20EOGenerator%20Templates/
and place them in a folder. In my case that was in
Inside this folder you will have two standard templates: _Entity.java en Entity.java. Do not change them for the moment.
(Additional templates and a reference are available here)
2. Go to Preferences > WOLips > EOGenerator
In EOGenerator Template Folder, fill in the folder you have placed the templates
In EOGenerator Java Template fill in _Entity.java
In EOGenerator Subclass Java Template fill in Entity.java
This is how it looks in my settings:
3. Go to the eomodel from which you want to create classes and subclasses in the WOPackage sidebar of Eclipse
4. Right click and choose WOLips Tools > Create EOGenerator File from the contextual menu, (it's a submenu)
Now a eogen file is created which has the name of the EOModel and an .eogen extension.
If there is already an eogen file, then another one will be created, with a number between the EOModel name and the extension.
The one with the highest number will be the newest (unless you decided to throw earlier ones away, then the numbering starts all over again).
5. Go to the eogen file, right click and choose EOGenerate... from the contextual menu.
If you have some definitions in your EOModel that have a Class Name that is not an EOGenericRecord, then the appropriate java class and subclass will be generated.
For instance: a Person class name in EOModel will result in a _Person.java file (which will be overwritten the next time EOGeneration will take place) and a Person.java file. The java file without the underscore is the file that will not be overwritten the next time. This file is the file that you would add your own methods. The next time the model changes, the _underscore.java file will be overwritten, but your methods are safe.
6. Check if everything worked out fine. If not (e.g. you made a typing error and a java file happens to be empty) throw away the generated file yo do not want, and restart the process.
7. If you are fine, you can start fine tuning your templates, or start defining templates per project.
making Velocity EOGenerator settings per project
1. Under Preferences > WOLips > EOGenerator
-> Remove all entries (this is not strictly necessary, but it rules out any errors at the project level)
2. Add a folder named templates in your project folder, inside of which you place your template files.
For starters, don't rename them. You can download them here:
Other options for Veogen to pick up any changes you wish to make to the templates:
- inside your eogen file you need to set template path to the folder containing _Entity.java, and if it's named something other than _Entity.java, you need to also set template name. Note that template name is ONLY a name, not a full path.
- or locate the template files in one of the paths that Velocity EOGenerator looks in by default (~/Library/Application Support/WOLips/EOGenerator/_Entity.java, for example).
3. Double check your model, so that none of your entities extend EOGenericRecord,
otherwise the generation gap pattern won't work, as the velocity generator generates all files,
rather than just those extending custom classes. this is a change from the old eogenerator. Also, your entities should be in packages for this all to work optimally. In the example "projectname.eo.class". When it was tried with no package (class) there were a number of errors in the resulting Java class files.
4. Create or edit your .eogen file, mine looks like this:
5. Double check, and open the .eogen file using open with > text editor. The whole command must all be on a single line; this is formatted for clarity:
6. If you are not seeing your entity files that start with the underscore character "_" in Eclipse, it is because you have them filtered out. Select filters from the down triangle in the package explorer:
7. Then uncheck 'EOGenerator _Files':