If you need a generalized solution, you can change your generated
methods to do exactly what you want through the template. This
would then give you all the functionality you want in the standard
generated methods.
With EOGenerator, you generate 2 class files. One is a subclass of
the other. This way, you never regenerate the file where your
business logic is, so you don't have to worry about merging after
changing your schema.
Ken
Yes, I did understand the concept of using another class file
generator instead of EOModeler, but did not get into EOGenerator
until half an hour ago. Didn't have need for it before. Anyway, I
assumed your two-class solution was a design idea for the problem at
hand, and not standard EOG behavior. And yes, assumptions *are*,
well, like having a nasty bug in java.lang.Object :)
Thanks for your help, everybody, I think I know now how to make this
work.
Best regards,
Flor
_______________________________________________
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]
