RE: EODatabaseContext.Delegate

Not at all.  If you can't handle it, just return null and the next in the
chain is invoked.  Introspection is quite fast; the overhead is
inconsequential relative to DB time.

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Zak Burke
Sent: Tuesday, May 23, 2006 2:06 PM
To: WebObjects Dev
Subject: Re: EODatabaseContext.Delegate

Zak Burke wrote on 5/23/06 12:36 PM:
> I have a particular EC save operation that needs to be reorganized
> (deletes need to happen before inserts). I have found
> EODatabaseContext.Delegate.databaseContextWillOrderAdaptorOperations(),
> but I can't figure out how to get to an EODatabaseContext from my
> EOEditingContext (EC).

Off-list, somebody pointed out that you can set a default delegate in,
say, Application.java to run when your app starts up:

EODatabaseContext.setDefaultDelegate(new MyDelegate());

That's a great start; it gives me a way to reorder all my operations.
Now, is there any way to do this only in particular circumstances?

I don't really want to set a *default* delegate; I want to set a
delegate for a particular transaction. Using a delegate for all
transactions, when it is only needed for a small percentage of them,
seems awfully inefficient.

zak.
_______________________________________________
WebObjects-dev mailing list
[email protected]
http://www.omnigroup.com/mailman/listinfo/webobjects-dev