• 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: Should ERXEC get sharedEC automagically?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Should ERXEC get sharedEC automagically?


  • Subject: Re: Should ERXEC get sharedEC automagically?
  • From: Chuck Hill <email@hidden>
  • Date: Tue, 21 Aug 2018 17:50:09 +0000
  • Thread-topic: Should ERXEC get sharedEC automagically?

See er.extensions.ERXEC.useSharedEditingContext at
https://wiki.wocommunity.org/display/documentation/Explanation+of+the+default+properties+in+a+Wonder+project

Did that fix it?

Chuck


On 2018-08-21, 9:43 AM, "Webobjects-dev on behalf of ocs@ocs"
<webobjects-dev-bounces+chill=email@hidden on behalf of
email@hidden> wrote:

    Hi there,

    the EOEditing context doc pretty unequivocally says

    ===
    By default, an editing context that has no shared editing context listens
for DefaultSharedEditingContextWasInitializedNotifications. If a notification
is posted while the context has no registered objects, the editing context sets
its shared editing context to the newly initialized default shared editing
context.
    ===

    Should it apply for an ERXEC, too? I sort of inferred it would, but by my
testing, it does not seem so: an ERXEC I make (through
ERXEC.newEditingContext()) seems to adamantly stay without
sharedEditingContext, although the notification is posted all right (I have
observed it myself to be sure), and if there's a good ole EOEditingContext, it
indeed duly sets its sharedEC at the time.

    Have I missed something of importance somewhere? The ERXEC documentation
does not say essentially anything of the sharedEC, far as I can say:

    http://wonder.sourceforge.net/javadoc/er/extensions/ERXEC.html

    In principle, I could work around the problem by setting the sharedEC to
all my ERXECs programmatically -- that works all right --, but it would be a
lot of work, with a danger I overlook something somewhere and got bit in the
tender parts by that...

    Thanks,
    OC

     _______________________________________________
    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


 _______________________________________________
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

  • Follow-Ups:
    • Re: Should ERXEC get sharedEC automagically?
      • From: "ocs@ocs" <email@hidden>
References: 
 >Should ERXEC get sharedEC automagically? (From: "ocs@ocs" <email@hidden>)

  • Prev by Date: Re: EOFetchSpecification .fspec plist description?
  • Next by Date: Re: Should ERXEC get sharedEC automagically?
  • Previous by thread: Should ERXEC get sharedEC automagically?
  • Next by thread: Re: Should ERXEC get sharedEC automagically?
  • Index(es):
    • Date
    • Thread