Guido,
Thanks for your tips. I know that putting the EOs in the default
package is dirty, but I'm trying to simplify the problem. I've tried
putting the EOs in a package and in the default package with the same
problems.
Which version of WOLips are you using?
3.3.4574
Here's the strange part – I've removed all references to the template
files in my project and Eclipse but WOLips is still picking up the
template files from somewhere.
I then edited the template files and I don't see the edits in my
generated EOs. Very odd.
I would have thought that the following eogen file would have failed,
but WOLips is picking up the template files from somewhere:
-destination src -model MyEOModel.eomodeld -subclassDestination src -
verbose -define-EOGenericRecord EOGenericRecord
- Joe
On Jan 26, 2008, at 23:39:27, Guido Neitzer wrote:
On 27.01.2008, at 00:22, Joe Moreno wrote:
I can't figure out where EOGenerator is picking up its template
files.
That is configured in the eogen file that is named like your model.
Oh, that helps! Thanks. I'm getting closer.
Interesting enough - I didn't have to do that.
So, I'm very close. But, I still get this as my first line:
package ${entity.packageName};
Perhaps I'm not setting the package or variable correctly?
Which version of WOLips are you using?
cug
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
