David Avendasora wrote on 4/5/07 2:32 PM:
I want to allow the user to move a RSComponent from one RoutingStep to
another. I present the user with a WOPopUpButton on each rsComponent of
all the RoutingSteps and they can simply pick which one they want it in.
It does update everything properly, but when the page comes back,
layout-wise the RSComponent is still in the original RoutingStep, but in
the database it is in the new RoutingStep (right where it's supposed to
be).
Why would the update be done properly, but the page not be fully updated
with the changes?
Because EOF loves its cache. Loves it, loves it, loves it. IMNSHO,
caching should be OFF by default because it's behavior is so
confusing: you run an update, see the changes in the DB, then run a
query and ... see no changes in the UI. WTF?
At any rate, try the following:
// assuming you construct a fetch-spec "f"
EOFetchSpecification f = new EOFetchSpecification(...);
f.setRefreshesRefetchedObjects(true);
and see if your UI gets properly updated.
Don't get me wrong, WO's cache handling is top-notch. But having
values cached when you haven't explicitly asked for that behavior is
downright confusing the first time you encounter it.
zak.
_______________________________________________
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]
