Re: Using composition instead of inheritance
Re: Using composition instead of inheritance
- Subject: Re: Using composition instead of inheritance
- From: Paul Hoadley <email@hidden>
- Date: Sun, 03 Jun 2012 13:03:15 +0930
On 03/06/2012, at 12:02 PM, Mike Schrag wrote: Not ..... Sure ... Maybe can you spit out the plist of the orig and construct a new one with that plist?
Thanks for the idea.
I pressed on for a bit after creating the attribute manually, and it mostly looked good until saving a new object, at which point I hit a duplicate primary key issue, presumably because the framework entity was still using the sequence originally created for it rather than the sequence for the app entity... (I had already created an AppEntity directly in code at first startup, and now D2W was going to create an AppEntity that it thought was a FrameworkEntity.)
I'm sure I could get there eventually, but it's starting to seem very complicated. I think I'll just revert to adding an attribute to the framework entity at runtime.
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden