An EnterpriseObject Design Question...
An EnterpriseObject Design Question...
- Subject: An EnterpriseObject Design Question...
- From: Kieran Kelleher <email@hidden>
- Date: Mon, 26 Dec 2005 14:58:26 -0500
Java interfaces allow us to implement flexible relationships between
objects or just plain flexibility using composition, but I am kinda
confused as to the best way to implement such relationships/composition
in my EOModel.
For example, let's say I have Entity A, B and C and each implements the
X interface. Now let's say I have entity G which by composition has a
to-one relationship with an object that implements the X interface. How
would I model that?
Would it require something custom like having two attributes in entity
G, namely 'typeXRelatedEntityName' and 'typeXRelatedEntityOid' and then
giving G custom attribute getter/setter [ x(), setX( X anObject) ] that
retrieves the related entity by fetching the single entity using the
two attributes? Is there anyone using a pattern like this or a better
one for persistent relationships to various objects that implement an
interface? Any gotchas/pitfalls?
Regards and thanks, Kieran
PS. I don't want to use inheritance since A, B and C are quite
different and I want the flexibility to add other entities that
implement interface X in the future.
_______________________________________________
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