Re: NSRecursiveLock.lock() causing deadlock??
Re: NSRecursiveLock.lock() causing deadlock??
- Subject: Re: NSRecursiveLock.lock() causing deadlock??
- From: Dov Rosenberg <email@hidden>
- Date: Thu, 28 Aug 2008 09:45:06 -0400
- Thread-topic: NSRecursiveLock.lock() causing deadlock??
Title: Re: NSRecursiveLock.lock() causing deadlock??
We actually do something like
NSNotificationCenter.defaultCenter().addObserver(this, connSelector, EOModelGroup.ModelAddedNotification, null);
To replace the model connection dictionary.
Dov
On 8/28/08 8:25 AM, "Jean-François Veillette" <email@hidden> wrote:
Le 08-08-28 à 08:12, Dov Rosenberg a écrit :
...
We replace the connection dictionary at startup. Could the difference in EOEditingContexts cause a second EOCooperatingObjectStore to be added?
If by "replace the connection dictionary at startup" you mean in 'Application' or something like that, then yes this will cause problem. I've seen some methods in EOUtilities reloading model, and thus reloading the connection dictionnary. You should not replace it at startup but at every model load (via notification, as what's being done in Wonder for example).
- jfv
_______________________________________________
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