On May 29, 2009, at 2:50 PM, Timo Hoepfner wrote:
Talking about notifications: I have a class registered in this app
that listens to some EOF notifications for a different entity (kind
of an audit trail for article stock). This particular entity is not
involved at all in the creation of orders, but could it be, that
when something BAD happens in an arbitrary listener of a
notification, the propagation of the notification is stopped without
getting any kind of exception?
It is possible, the notifications are sent synchronously. The sending
thread would be blocked if a notification receiver blocked. But I'd
expect you to notice severe other problems.
Chuck
Timo
Am 29.05.2009 um 23:29 schrieb Timo Hoepfner:
On May 29, 2009, at 2:04 PM, Timo Hoepfner wrote:
Anyone? Please? PLEASE?
You could add an object to log ALL notifications and see if one is
coming at a particular time to cause this.
An EOEditingContext subclass can be created to log the start and
top of operation and when notification from other ECs or the
ObjectStore are received. It sure sounds like a notification is
causing the EC to lose track of state.
I also think it might be something wonky related to notifications.
Will try to make an omnipotent notification observe. The art will
be to read it's output...
Thanks again,
Timo
_______________________________________________
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/th-dev%40onlinehome.de
This email sent to [email protected]
--
Chuck Hill Senior Consultant / VP Development
Come to WOWODC'09 in San Fran this June!
http://www.wocommunity.org/wowodc09/
_______________________________________________
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]
