Hey guys, I’ve been using Wonder’s augmented transaction methods in combination with notifications to encourage a loosely coupled design. Over time, I've been increasingly applying this kind of solution on my systems. Now, I'm facing a problem when expecting to produce notifications for recurring EO changes. Basically, I expect the invocation of the willUpdate method on a second EO changed during the willUpdate phase of a former EO. However, in that scenario, the second EO willUpdate method is never invoked.
I've seen that the CooperatingEditingContext described in the Practical WebObjects book does exactly what I want. So, is there a reason to not support notifications for recurring changes (i.e. avoid notification cycles)? Is the current behavior expected? Or is it a misbehavior? Cheers, Henrique _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
