Hey John,
On Jul 15, 2009, at 00:38, John Ours wrote:
I am not able to reproduce this problem unless I push the EC to the
server without saving it to the database (RMI for example). Baring
that though I cannot reproduce the concurrency issue with either two
copies of the client on one machine or two separate machines. With
locking off on all the attributes I'm getting last-in-wins behavior
as expected.
Interesting...
Is this the scenario in your app, ECs being pushed to the server
dirty and uncommitted?
No, the error occurs on calling save changes on the second client
(after the first client has successfully saved changes)...
Even when I simulated that, I was able to catch the exception from
saveChanges in client2, revert that context, and client1 was able to
save as expected.
Argh, so things are working as expected for you... Hm, I do some
fussing with session's default context, replacing it with my custom
EC, perhaps that is causing this to happen. I will try this out again
using the standard setup.
Also, what is your setup? I am on 5.4.2, no Wonder.
Thanks for trying this out, this helps a lot, now I know I should
focus on my stuff instead of the frameworks!
F
_______________________________________________
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]
