Re: EOF bug?
Re: EOF bug?
- Subject: Re: EOF bug?
- From: "Morris, Mark" <email@hidden>
- Date: Mon, 13 Aug 2018 16:56:01 +0000
- Thread-topic: EOF bug?
If it’s true that Wonder hasn’t patched _EOExpressionArray, I guess the
simplest solution would be to add an implementation of objectsNoCopy() there.
It looks like it might be as simple as:
protected Object[] objectsNoCopy() {
return _array.objectsNoCopy();
}
-- Mark
From: Webobjects-dev
<webobjects-dev-bounces+mark.morris=email@hidden> on behalf of
"Morris, Mark" <email@hidden>
Date: Monday, August 13, 2018 at 9:24 AM
To: Samuel Pelletier <email@hidden>
Cc: "email@hidden" <email@hidden>
Subject: Re: EOF bug?
Hi Samuel,
Thanks for the response!
Sorry, it was a long night. The problem does indeed occur when objectsNoCopy()
returns null, even though there are objects in the EOExpressionArray. However,
the method directly in EOAttribute is actually addObjectsFromArray(), which
calls objectsNoCopy() in its implementation.
Regards,
Mark
From: Samuel Pelletier <email@hidden>
Date: Monday, August 13, 2018 at 6:31 AM
To: "Morris, Mark" <email@hidden>
Cc: "email@hidden" <email@hidden>
Subject: Re: EOF bug?
Hi Mark,
I checked my version of EOAttribute and was unable find call to objectsNoCopy()
in the code. I checked the WO and ERAttributeExtension versions of the class.
Are you on an older version of WO ?
Samuel
Le 13 août 2018 à 05:32, Morris, Mark
<email@hidden<mailto:email@hidden>> a écrit :
Hi all,
After much time and effort, I’ve traced a problem in my code to what appears to
be a bug in EOF’s _EOExpressionArray.
Let me state first that we’re way behind in our Wonder version, so it’s
possible that Wonder has fixed this already, but a quick search didn’t find it.
(We’re planning to catch up to current in the next few months.)
The problem seems to stem from the fact that _EOExpressionArray extends
NSMutableArray, but it doesn’t reimplement objectsNoCopy(). This is a problem,
because _EOExpressionArray uses it’s own internal array, not the superclass’s.
There’s a critical point in EOAttribute._normalizeDefinitionPath() where
objectsNoCopy() is called but returns null, even though the _EOExpressionArray
has elements, because it’s referencing the superclass array instead of the one
local to _EOExpressionArray.
Has anyone seen this? Has it been patched? Thanks!
Regards,
Mark
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list
(email@hidden<mailto:email@hidden>)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden<mailto: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
| References: | |
| | >EOF bug? (From: "Morris, Mark" <email@hidden>) |
| | >Re: EOF bug? (From: Samuel Pelletier <email@hidden>) |
| | >Re: EOF bug? (From: "Morris, Mark" <email@hidden>) |