If you use ERXRunnable, then you still get autolocking. Just don't try to pass an existing EC or EOs to a background thread. Pass EOs by global id and create the EC on the thread.
See also Kieran's most recent WOWODC presentation on ERXExecutor stuff and background thread processing. Ramsey On Feb 10, 2012, at 9:30 AM, Michael Gargano wrote: > Hi everyone, > > I just want to get clarification on something before I get myself into > trouble later. If I have a headless WO app (or potential just a spawned > worker thread), and I'm using ERXEC, I need to manually lock and unlock the > context, correct? I'm assuming that ERXEC does the autolock/autounlock in > the RR loop, which I won't have in this situation. > > Thanks. > -Mike > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/webobjects-dev/rgurley%40smarthealth.com > > This email sent to [email protected] _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
