On Nov 30, 2007, at 9:35 AM, James Cicenia wrote:
> OK -
>
> I finally had to modify a model. I have used EOGenerator with great
> success for years now.
>
> Now after reading the list I am a bit confused. Can I still use it?
> Should I? I followed the wike on EOGenerator and
> it doesn't seem to work for me.
>
> What are people doing now?
>
> Is EOGenerator not compatible with Leopard?
>
> FINALLY, why don't I see my posts anymore on this or the webobjects
> list? What the heck did I or Leopard do?
History:
EOModeler had built in code generation, which always sucked,
because it didn't use the 1 generation removed 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 5.4, not sure about 5.3/Leopard but
I think so. It uses MiscMerge templates, an open source objc library.
What people are calling JavaEOGenerator is an Apple replacement
that uses WO style templates (.html, .wod, etc.), which means its
actually written as a .woa. It uses the WO code to parse the model. I
was unable to get it to run, but I didn't try that hard. 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 its 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.
Pierce
This archive was generated by hypermail 2.0.0 : Sat Dec 01 2007 - 15:16:10 EST