Re: References accross models

Subject: Re: References accross models

From: Tonny Staunsbrink <email@hidden>

Date: Mon, 18 Dec 2006 11:42:53 +0100

Delivered-to: email@hidden

I tried inluding Wonder (the 3.0 download). That didn't solve the issue either. I don't think issue is the sequence of the entities. But the fact that that some entities now live in af Different EODatabase. Before the the entity was only living in separate model, now they also lives in different Databases. I've looked for som way to hook into the way the faults are resolved at this, level but i haven't found anything so far, except maybe subclassing one of the EOAccessGenericFaultHandler subclasses, which seemed like a major task (for the time being).

Anyhow, the problem is solved for now by having my EOCustomClasses handle faulting and setting the foreign key manually. Something like:

public void setMyEntity(MyEntity entity){

Object value = EOUtilities.primaryKeyForObject(object.editingContext(), object).allValues().objectAtIndex(0);

takeValueForKey(value, "myEntityFK");

}

public MyEntity getMyEntity(MyEntity entity){

return (Product)EOUtilities.faultWithPrimaryKeyValue(editingContext(), "MyEntity", valueForKey("myEntityFK"));

}

Maybe I'll look into the fault handlers later....

Cheers

/Tonny

On Dec 15, 2006, at 3:23 PM, Mike Schrag wrote:

If you use Project Wonder, this gets wired in automatically. So if you're already using a recent version of Wonder, then this probably ISN'T the fix. If you're not, then you might just be able to steal its implementation and try it.

On Dec 15, 2006, at 8:59 AM, Francis Labrie wrote:

Hi,

Mike Schrag wrote:
BTW, I think Project Wonder might have a fix for this bug ... ERXModelGroup.checkInheritanceRelationship gets wired up automatically, and it sounds like it MIGHT be a fix for this problem:

/**
* Corrects a strange EOF inheritance issue where if a model gets loaded and an entity that has children located in
* a different model that hasn't been loaded yet will not be setup correctly. Specifically when those child entities
* are loaded they will not have their parentEntity relationship set correctly.
*/

Interesting: I'll try this fix to see if it works for all cases. Thanks!

--
Francis Labrie
Saint-Bruno-de-Montarville, Quebec, Canada

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/email@hidden

This email sent to email@hidden

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/email@hidden

This email sent to email@hidden

_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/email@hidden This email sent to email@hidden

References:

>References accross models (From: Tonny Staunsbrink <email@hidden>)

>Re: References accross models (From: Francis Labrie <email@hidden>)

>Re: References accross models (From: Mike Schrag <email@hidden>)

>Re: References accross models (From: Francis Labrie <email@hidden>)

>Re: References accross models (From: Tonny Staunsbrink <email@hidden>)

>Re: References accross models (From: Mike Schrag <email@hidden>)

>Re: References accross models (From: Francis Labrie <email@hidden>)

>Re: References accross models (From: Mike Schrag <email@hidden>)