The WOLips EOGenerator is an integral part of WOLips and shares its codebase with Entity Modeler. It uses release 1.5 of the Velocity Templating Engine and template files that use the Velocity Template Language. This templating language is similar to the original Rubicode EOGenerator that many developers used with WebObjects 5.3 and earlier so migrating old templates to the new language is time consuming, but not difficult.
If you don't specify a custom template name in your .eogen file, then the WOLips EOGenerator will simply use the built-in ones. This is the way all developers should start out. You can always grab those templates and modify them, or use some of the many modifications shared by other WebObjects developers on the EOGenerator Templates and Additions page.
There are two ways: create eclipse-wide settings, or create settings per project.
Note: There is actually no need to download Mike's templates as described below unless you want to customize them. WOLips includes two sets of default templates in the .jar files (so don't bother searching your file system for them) - one as described below and another for use with WOnder. If you are using WOnder, you need to follow Mike's instructions for their use: "Where it says "Entity.java" and "_Entity.java" you can use WonderEntity.java and _WonderEntity.java ... If your individual .eogen files override that, you will have to set it in there also". If you leave the "EOGenerator Template Folder" field empty, it will use the default templates...
eclipse-wide settings for EOGeneration
1. Download the templates that Mike Schrag made from httphttps://webobjectsgithub.mdimension.com/wolips/EOGeneratorwolips/Velocity%20EOGenerator%20Templates/tree/master/wolips/core/plugins/org.objectstyle.wolips.eogenerator.core/templates
and place them in a folder. In my case that was in
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)