ERModernDirectToWeb and custom relationship keypaths
ERModernDirectToWeb and custom relationship keypaths
- Subject: ERModernDirectToWeb and custom relationship keypaths
- From: Tim Worman <email@hidden>
- Date: Mon, 30 Aug 2010 16:34:16 -0700
I am using an existing model framework to drive a new ERModernD2W interface. So, as an example, let's say I have a relationship defined like
foo <-->> bar
foo.bar() returns all related records. But my frameworks have custom accessors that may return a more qualified set of data that users of my apps would be expecting. So I have methods like:
foo.getBarForFoo()
which filters certain un-needed results out. Most of my app would use the latter but sometimes I'd still want to use the former. But if I use "getBarForFoo()" in a D2W rule the relationship results just look like EOGenericRecord strings. So maybe D2W doesn't know what entity is being returned?
Since not all my apps are D2W I don't want to change the signatures of these methods just to satisfy the places where D2W is used. I do want the restricted results. Does the rule system have a way of handling this?
Tim Worman
UCLA GSE&IS
_______________________________________________
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