Re: Inherited Relationships using Different Destinations
Re: Inherited Relationships using Different Destinations
- Subject: Re: Inherited Relationships using Different Destinations
- From: David Avendasora <email@hidden>
- Date: Fri, 5 Sep 2008 09:41:47 -0400
On Sep 5, 2008, at 8:21 AM, Mike Schrag wrote:
I was just using it as an example of the type of addition that
would need to be made. Or am I missing some existing api that will
give me the EORelationship from the Parent?
Never tried, but does
$
entity
.parent.getRelationshipNamed(relationship.name).destination.name work?
I didn't realize that you could pass values in through the templates.
That would make it really easy. I saw the getRelationshipNamed(String)
in the code, but didn't think I could pass in the relationship name
from the template. You know, pretty soon Veogen is going to catch
on... ;-)
oh nevermind .. I just committed
relationship.getParentRelationship ... It's only in the new branch,
though, so you'll need to wait to switch to get it (I'm sort of done
merging branches :) ).
Mike, you rock. I can't believe you merged branches for as long as you
did. I'm in the middle of deploying new versions of my Apps. Once that
is done, I'll check out NewHotness. Then again, the way things are
going for me right now, NewHotness will be Stable by the time I get to
it. :-/
Dave
_______________________________________________
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