You can add the relationships programmatically, when your framework
loads for example.
Cheers, Anjo
Am 05.08.2008 um 19:23 schrieb Florijan Stamenkovic:
Hi all,
Maybe this was discussed already, but googling didn't help.
What I could use in our biggest app is splitting the model into
inter-dependent frameworks. However, what happens if we want to
deploy an app that utilizes only some of the frameworks?
Example:
FrameworkA contains entity Person
FrameworkB contains entity PhotoOfPerson
Person <->> PhotoOfPerson
PhotoOfPerson depends on the Person, since it has a to-one mandatory
relationship, but Person does not depend on PhotoOfPerson.
Let's say we want to deploy an app that only deals with Person
records, and not their photos. Ideally we would only use the
FrameworkA in the deployment project. It seems to me that it is very
difficult to make this happen. Assuming of course that the Person -
>> PhotoOfPerson is modeled.
Does anyone do this, somehow? Or should relationships across model
frameworks be avoided?
Thanks,
F
_______________________________________________
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/anjo%40krank.net
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]
