On Jun 2, 2006, at 12:46 PM, Ken Anderson wrote:
Usually when I have a bug like this, there's a relationship somewhere
to an object in a different editing context. Are you sure that
everything is in the same context? I realize your code example is,
but often that's not the whole picture.
There is, but everything I do has the same context. I have a page for
browsing actors (one editing context), and another component which does
this stuff with actor's movie and it uses its own component (but first
I do localInstanceOfObject() on actor)
I played with it a bit more today... and I found this one working:
ec.saveChanges();
if (old value != new value) {
movie.setIsReallyCool(old value); // yes, this is the OLD
value, so saveChanges does nothing
ec.saveChanges();
movie.setIsReallyCool(new value);
ec.saveChanges(); // and this one finally saves the data...
}
--
Regards,
Adam Czysciak
[EMAIL PROTECTED]
_______________________________________________
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]
