Re: difficulties with cross-model relationship
Re: difficulties with cross-model relationship
- Subject: Re: difficulties with cross-model relationship
- From: Mike Schrag <email@hidden>
- Date: Sat, 21 Mar 2009 10:15:26 -0400
Can't do it like that. You could add a method employees() to
LDAPEmployee that did a qualified fetch perhaps.
Hmm, seems like it becomes less and less useful to model it. Without
any restricting qualifier I can't have LDAPEmployee at all - since a
restricting qualifier is necessary. I could just model FacultyUser,
StaffUser, etc. to inherit directly from InetOrgPerson and put the
appropriate restricting qualifiers on "employeeType" but those are
both of the type EmployeeUser. I really want to have that super
class in there. Is there a way to accomplish this that I'm not
grokking?
This is a common case where inheritance seems right but is often not
really ... Typically this is situation is better modeled as roles on a
single "person" class. For instance, what do you do if employeeType
changes? EOF would be really displeased with that, and mutable
classes is usually a red flag of a design issue.
ms
_______________________________________________
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