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
<[email protected]> on behalf of
"Morris, Mark" <[email protected]>
Date: Monday, August 13, 2018 at 9:24 AM
To: Samuel Pelletier <[email protected]>
Cc: "[email protected]" <[email protected]>
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 protected]>
Date: Monday, August 13, 2018 at 6:31 AM
To: "Morris, Mark" <[email protected]>
Cc: "[email protected]" <[email protected]>
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 protected]<mailto:[email protected]>> 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 protected]<mailto:[email protected]>)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/samuel%40samkar.com<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.apple.com_mailman_options_webobjects-2Ddev_samuel-2540samkar.com&d=DwMFaQ&c=BNNF-YNv0CLLslhP2Bcx5Q&r=R0ZqsewJs3eSJk7vLCqZv0r5kJlLXQLnGTeg9t8MlqA&m=AdvAfKTkUyccvBpaKhr9GvlfY3653NxMU8J5XO6ue2A&s=yDB_Rzh491N9j7il8RMpWcTkZo6Q_-nHy8gitXhx_28&e=>
This email sent to [email protected]<mailto:[email protected]>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
