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 (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
