Re: Qualifier Evaluation with Object in Multiple Editing Contexts
Re: Qualifier Evaluation with Object in Multiple Editing Contexts
- Subject: Re: Qualifier Evaluation with Object in Multiple Editing Contexts
- From: Paul Hoadley via Webobjects-dev <email@hidden>
- Date: Thu, 19 Nov 2020 15:10:24 +1030
On 12 Jun 2019, at 11:54 pm, Henrique Prange via Webobjects-dev
<email@hidden> wrote:
> "That's a code smell" was my first thought as well. I tried to pass on the
> same editing context among all the components involved in this operation.
> However, considering the level of abstraction of the system and the
> disconnection between the components, sharing the same editing context turned
> out to be a bad idea too.
I just ran into this issue again today. As I noted earlier in this thread, I've
previously been able to solve it by some judicious calls to localInstanceIn(),
but this time, much like Henrique above, I was several layers of abstraction
above where I needed to be, and faced the prospect of some multi-level API
re-writes, until...
> As an alternative, I thought about local instancing the EOs into the correct
> editing context. Unfortunately, at the time of writing the first email, I
> wasn't aware of the ERXEOControlUtilities.localInstancesInQualifier method.
> This method traverses the qualifier hierarchy doing precisely that and would
> have solved my problem.
I just used localInstancesInQualifier() for the first time ever. Thanks
Henrique!
> In the end, I think the answer to "is it a bug?" is in the eye of the
> observer.
I still can't convince myself that this _isn't_ a bug.
--
Paul Hoadley
https://logicsquad.net/
https://www.linkedin.com/company/logic-squad/
_______________________________________________
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