Maybe the Strategy design pattern could be used instead of inheritance
and the Strategy behaviour becomes a selectable "behaviour" attribute
of entity "Batch" instead of using subclass types. If you are unsure
what the Strategy design pattern is, see Head First Design Patterns
book pages 15-24.
Regards, Kieran
On Nov 30, 2008, at 8:29 PM, Ted Archibald wrote:
I have a question about eo inheritance.
Let's say I have the following three entities:
Entity Batch - Table Batch - Class Batch extends ERXGenericRecord -
qualifier typeId = 1
Entity SubBatch1 - Table Batch - Class SubBatch1 extends Batch -
qualifier typeId = 2
Entity SubBatch2 - Table Batch - Class SubBatch2 extends Batch -
qualifier typeId = 3
Now, if I change the typeId of an eo will this cause problems and
or make WebObjects angry? From the experiments I've done it doesn't
seem to cause any problems, but down the road will this have
negative consequences?
_______________________________________________
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]
