.... and boy is it easy to add new flavors of behaviour ... no need to
touch the EOModel if the attributes are the same or a subset of the
EO's attributes.
On Dec 4, 2009, at 9:27 AM, Kieran Kelleher wrote:
I don't use EOModel inheritance any more. It is a PITA. Not worth
the hassle. Using Strategy design pattern to composite in different
behaviours works better for me. Remember the OO Principle "Favor
composition over inheritance" ... I now favor composition over
inheritance ;-) BTW, for this setup the table is identical to a
single-table inheritance table, except that the 'type' id field
determines the lazily constructed strategy behaviour class for the
EO. I will only ever use EOModel inheritance again, if (1) I am told
to by a customer, or (2) Strategy design pattern behaviour
composition simply does not make sense (so far it makes sense for
every case I have looked at in last few years) YMMV ;-)
Regards, Kieran
On Dec 4, 2009, at 8:49 AM, David Avendasora wrote:
Or you can just not use Vertical Inheritance. :-)
_______________________________________________
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/kieran_lists%40mac.com
This email sent to [email protected]
_______________________________________________
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]
