• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
RE: EditingContext problem
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: EditingContext problem


  • Subject: RE: EditingContext problem
  • From: <email@hidden>
  • Date: Fri, 23 Apr 2004 09:39:19 +0200
  • Thread-topic: EditingContext problem

Chuck,

> Is that worse than com.webobjects.eoaccess.EOEntityClassDescription
> inheriting from com.webobjects.eocontrol.EOClassDescription? There are
> already cross/circular dependancies there.

I have no problem with the EOAccess layer depending on the EOControl layer. EOAccess' only reason for being is to provide persistence for an EOControl layer. In fact, there are many occasions where EOAcces is dependent on EOControl by implementing interfaces required by EOControl. E.g. an EODatabaseContext is an EOCooperatingObjectStore.

EOControl however may be stacked above different persistence layers. Apple provides two: EOAccess and EODistribution. Relying on EOAccess in an EO will break this. Additionally this would introduce circular dependancies between those layers and ultimately between elements of your own code.

The worst thing here is that over merely using a method as common as createAndInsertInstance() in an EO one bars it from ever being reused in a JavaClient application.

>> - 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.

It seems like I stand corrected on this one. Odd thing is that I have the distinct recollection of passing null for editing context to a few EOUtilities methods. A quick look at the documentation now finds only methods where the editing context is redundant with the fact that a second argument takes an enterprise object.

Pierre


**********************************************************************
This email and any files transmitted with it are intended solely for
the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the sender
of this message. (email@hidden)
This email message has been checked for the presence of computer
viruses; however this protection does not ensure this message is
virus free.
Banque centrale du Luxembourg; Tel ++352-4774-1; http://www.bcl.lu
**********************************************************************
_______________________________________________
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.


  • Prev by Date: Re: best way to display large set of data using wotable
  • Next by Date: Re: Using name and email address in WOMailDelivery
  • Previous by thread: Re: EditingContext problem
  • Next by thread: Object property initialization problem
  • Index(es):
    • Date
    • Thread