Hi Dave,
Thank you for your help. I was led to think that a one to many relationship could be flattened like a many to many can. Proved is I was wrong assuming it.
Regarding the model I am trying to implement, I am modeling my application after Len Silvertston's book, "The Data Model Resource Book". I regard his models and suggestions very valuable.
This specific model, Party ->> ContactMechanism -> Email or -> Phone or -> PostalAddress suits my needs very well. The different uses of addresses or phones will be modeled with another entity, ContactMechanismPurpose, which the user can change as needed. So when a user wants to change a billing address it will be a trivial change in the relationship ContactMechanism -> ContactMechanismPurpose. Currently, I have not yet implemented the contact mechanism purpose entity, but I have implemented ContactMechanismType, where the type can be phone, FAX, business email, home email and so on.
My problem with this approach is that I want to rely on Modern D2W to build my application without writing custom components if possible. In the case of the to many and optional to one relationships Party ->> ContactMechanism -> Email I am very frustrated for not being able to find a way to use one of the most wonderful components in Wonder, ERMODEditRelationshipPage.
I accept suggestions on how to instruct ERMODEditRelationshipPage to create the whole entities path to solve models like Party ->> ContactMechanism -> Email.
As a matter of fact, I've been thinking of writing a custom component to edit relationships to entities like phones and emails like the UI in the iPad "Address Book". The way it uses the small + and - buttons and the popup for the type is very inspiring.
Angelo
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