Also remember that ERXEC only auto-locks for request/response loops. You are responsible for manually locking in background threads.
Not exactly. It only doesn't unlock until you call ERXEC.unlockAllContextsForCurrentThread(). So depending on the complexity of your thread, it's easier to subclass ERXRunnable and implement _run() which does this and a bit more.
Cheers, Anjo _______________________________________________ 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]
