Found workaround for Java Client problem
Found workaround for Java Client problem
- Subject: Found workaround for Java Client problem
- From: Nick Pilch <email@hidden>
- Date: Mon, 16 Dec 2002 19:07:19 -0800
I had a breakthrough with my Java Client problem. It seems that I
could cause the server exception to go away by removing the deletion
of one object from my saveChanges() operation.
The particular operation I was studying is complex with a number of
updates, insertions and deletions of related objects happening at
once. Perhaps this complexity and/or the complexity of my model is
causing the server code to freak out.
Fortunately, I can do the deletion in another saveChanges() right
after the first operation.
This problem has plagued me since WO 4.51 and seems to be present in
5.1 and 5.2 as well. I assume it's the same problem I saw in WO 4.51.
It was the same exact symptoms and same error message, but it wasn't
possible to see the server backtrace in WO4.51 when doing Java Client
work.
Thanks to everyone who helped out.
--
Nick Pilch / email@hidden
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.