Re: Optimistic locking failure on insert
Re: Optimistic locking failure on insert
- Subject: Re: Optimistic locking failure on insert
- From: "Jerry W. Walker" <email@hidden>
- Date: Wed, 15 Mar 2006 16:13:05 -0500
On Mar 15, 2006, at 4:01 PM, Chuck Hill wrote:
I think so. The exception that Ian posted is not the
EOGeneralAdaptorException that you are thinking of. It is thrown
by EODistributionContext. EODistributionContext is not an editing
context. "EODistributionContext objects perform the server-side
related work behind Java Client applications and take care of
encoding and decoding enterprise objects and other data. ...
EODistributionContext objects track the state of the server side
object graph and communicate changes to the client, thus keeping
the client and server object graphs in sync." It appears to me
that what is happening is that when the update arrives at the
server, the EODistributionContext somehow decides (erroneously, it
would seem) that it is based on an out of date snapshot. Once
once it passes the EODistributionContext would it get to an edting
context, EOF stack, and the database. All of this based on my
rather limited understanding of the JavaClient architecture.
Oops. More coffee!
--
__ Jerry W. Walker,
WebObjects Developer/Instructor for High Performance Industrial
Strength Internet Enabled Systems
email@hidden
203 278-4085 office
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden