On Dec 4, 2009, at 6:27 AM, Kieran Kelleher wrote:
I don't use EOModel inheritance any more. It is a PITA. Not worth
the hassle.
I've never found that to be the case. What trouble were you having?
Chuck
Using Strategy design pattern to composite in different behaviours
works better for me. Remember the OO Principle "Favor composition
over inheritance"
That is "Favor" not "use even when inheritance is appropriate".
Chuck
... 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 (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/chill%40global-village.net
This email sent to ch...@global-village.net
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
