Re: Reporting Java Client EC save exceptions
Re: Reporting Java Client EC save exceptions
- Subject: Re: Reporting Java Client EC save exceptions
- From: Florijan Stamenkovic <email@hidden>
- Date: Fri, 9 May 2008 10:24:57 -0400
On May 09, 2008, at 04:25, John Pollard wrote:
On which context did you put that delegate? On the
EODistributionContext's editing context? That is where it should
go, and I find it very weird that the delegate should not be
performing...
I put the delegate on the default Session EC which I create myself
at the start of a new session. I was under the impression that each
client connected has their own session EC and that that is used to
handle all requests, is that not the case?
Uhm, I guess that a session for a JC has an editing context (a
Session always does, no?), but that is not the editing context that
is in between the client and the database. EODistributionContext's
editing context is the one you need to deal with. I believe you could
solve this situation exactly the way you first thought of it (with an
ec delegate), unless what Dave suggested works better in your
situation...
See the com.webobjects.eodistribution.EODistributionContext API,
specifically the DistributionContextInstantiatedNotification
constant. I believe you need to register for that notification, and
when it's posted you can add an EditingContext delegate to the ec of
the distribution context. That should do what you want, please let us
know if it does.
HTH
F
_______________________________________________
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