Re: Flattened Relationships and storedValueForkey()
Re: Flattened Relationships and storedValueForkey()
- Subject: Re: Flattened Relationships and storedValueForkey()
- From: Florijan Stamenkovic <email@hidden>
- Date: Thu, 30 Oct 2008 15:38:17 -0400
On Oct 30, 2008, at 05:24, David Avendasora wrote:
On Oct 25, 2008, at 10:42 AM, Florijan Stamenkovic wrote:
Without knowing exactly what the problem is, I'd just suggest that
you skip flattening in the model, and do it in Java. You'll avoid
this problem, and you'll also have more control over value caching
(which could be what is producing the erroneous result). While
getting the same result.
All the reasons for putting them in the model revolve around
convienience, not actual added functionality. Having them in the
model gets me some added love from D2JC being able to determine the
Class and therefor automatically pick the right UI screen for the
result set.
Ah yes, I keep forgetting that you're using D2JC.
Also, if you're doing this on the client, I definitively recommend
using JBND to do it, you'll get (for 5 lines of code or something):
- lazy init of the flattened value
- value caching
- automagic change detection and refreshing (when a relevant
change on the keypath changes the cache is release and the value
re-evaluated next time you ask for it)
You know, I've always thought that implementing JBND would mean I'd
have to not be doing D2JC anymore. I wonder if it will work with
D2JC as I'm already subclassing EOGenericRecord to add some things...
They should not clash, but a D2JC generated interface will not use
the strongest points of JBND: data binding, change notification,
filtering, the (new and unpublished) undo / redo stuff... You'd get
some minor stuff though...
F
_______________________________________________
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