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 PROTECTED]> 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 EOCooperatingObjectS >> tore 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 protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
