• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Using composition instead of inheritance
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Using composition instead of inheritance


  • Subject: Re: Using composition instead of inheritance
  • From: Mike Schrag <email@hidden>
  • Date: Fri, 01 Jun 2012 08:56:14 -0400

Remove FrameworkPerson entity, then rename AppPerson to be FrameworkPerson.

Sent from my iPhone

On Jun 1, 2012, at 3:30 AM, Paul Hoadley <email@hidden> wrote:

Hi Mike,

On 30/05/2012, at 8:01 AM, Mike Schrag wrote:

When your models load, replace FrameworkPerson entity with AppPerson entity, so fetches for FrameworkPerson are secretly the equivalent to what AppPerson fetches would be.

Is this just a matter of calling removeEntity() and then addEntity() on the EOModel, or is there more that needs to be done?


-- 
Paul Hoadley
http://logicsquad.net/



 _______________________________________________
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

  • Follow-Ups:
    • Re: Using composition instead of inheritance
      • From: Paul Hoadley <email@hidden>
References: 
 >Re: Using composition instead of inheritance (From: Paul Hoadley <email@hidden>)

  • Prev by Date: plist
  • Next by Date: Re: Using composition instead of inheritance
  • Previous by thread: Re: Using composition instead of inheritance
  • Next by thread: Re: Using composition instead of inheritance
  • Index(es):
    • Date
    • Thread