Hi Guido,
Thanks for the feedback. It helps to know that other people are able
to get this to work as advertised. Regarding "it was always a
problem in my code so far", do you remember what kinds of problems in
your code led to problems like the one I'm having? Maybe I'm doing
the same thing.
Mike Schrag wrote earlier in this thread that you have to explicitly
turn on locking in project wonder. To my knowledge I am not doing
this. How do you go about that? I will give that a try and see what
happens.
Mark
On Apr 22, 2007, at 1:59 PM, Guido Neitzer wrote:
On 22.04.2007, at 11:39, Steven Mark McCraw wrote:
My understanding regarding ERXEC is the same as yours, and even
reading through the Project Wonder code, I get the strong
impression that it should work everywhere. But if I comment out
my locking code and add the following to my application constructor:
NSLog.allowDebugLoggingForGroups
(NSLog.DebugGroupEnterpriseObjects |
NSLog.DebugGroupMultithreading);
I get output everywhere that I am using an editing context without
a lock. So I'm a little afraid to leave it that way.
Sorry to say that, but than still something seems to be screwed up
in your environment. I'm not saying that you're doing something
wrong as I really don't know that, but I found that the Wonder
(ERXEC) locking stuff and also nested editing contexts "just work"
in about two dozen applications we are using with that.
Nevertheless, I still think you're abusing something somewhere just
because of the fact, that so many other people use Wonder, the
locking stuff in there, nested editing context and so on without
any problems.
And if I found a problem like the one you're seeing it was always a
problem in my code so far.
cug
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
