Re: EditingContext problem
Re: EditingContext problem
- Subject: Re: EditingContext problem
- From: Chuck Hill <email@hidden>
- Date: Thu, 22 Apr 2004 10:43:28 -0700
On Apr 22, 2004, at 12:36 AM, <email@hidden> wrote:
EOUtilities is your friend:
Sorry, I can't let this stand as is. EOUtilities is pure evil:
No, that's DirectConnect. ;-)
- It mixes EOControl & EOAccess utility methods in one single class.
This actually should prohibit its use from within the EOControl layer
- that includes EOs. What a shame! Worse it tempts developers
introduce a reverse dependancy between EOControl & EOAccess.
Is that worse than com.webobjects.eoaccess.EOEntityClassDescription
inheriting from com.webobjects.eocontrol.EOClassDescription? There are
already cross/circular dependancies there.
- It's API is polluted by its historic background. Many of the methods
taking an EOEditingContext for argument could do without.
Which methods are you thinking of? The reason that they take an
EOEditingContext is to handle the case where there are multiple EOF
stacks.
Chuck
_______________________________________________
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.