My vote would be for Mike's version. Though his uses Entity
Modeler's "EOF" stack and JavaEOGenerator uses real EOF. I like the
templates that Mike's uses better (Velocity) and the fact that you
don't need to launch an entire WO App to generate some text files.
Chuck
On Nov 15, 2007, at 12:55 PM, Pierce T. Wetter III wrote:
>
>
> Now that the JavaEOGenerator source has been released, I vote for
> slurping the necessary bits into woproject.
>
> Why:
>
> I tried installing/running it the other day and basically never
> succeeded so I just ended up using the one Mike built in once I saw
> the posting indicating it was there. (Yay, Mike!) It seems like
> code generation is a key feature of Entity Modeler/EOF, so it makes
> sense to have it both built in, and have standardized templates
> also installed. Perhaps we could even make it relatively foolproof
> and have it auto-detect which template format its using or have
> that be a command line parameter.
>
> Just my $0.02 having undergone recent pain with the whole issue.
> Of course, this assumes that the Apple version is in some way
> superior to the Mike version, which I'm not sure is true, and it
> certainly doesn't feel that way. So I guess what I'm saying by
> "necessary bits" above, is that perhaps someone can just confirm
> that it doesn't do anything that the Mike version
>
>
>
>
> Pierce
>
> http://developer.apple.com/samplecode/JavaEOGenerator/index.html
>
--Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems. http://www.global-village.net/products/practical_webobjects
This archive was generated by hypermail 2.0.0 : Thu Nov 15 2007 - 16:01:56 EST