Oooops.
With Daryl's help I managed to track down the problem. Turns out I
had a method in my server side Project class that was overriding a
relationship, and retuning an NSArray (immutable). The code is old,
and should have been kicked out when I decided to actually model the
relationship and not just derive it in Java from another one... After
I modeled the relationship, EOF rightfully expected to get a mutable
array when asking for the prop.
Moral of the story? Maintaining two sets of EO classes (server and
client) can be tricky. And one should not be dumb enough to change
one, and not change another. Well, this is the first time this
particular JC issue kicked me in the ass, but I believe other JC
developers will be able to relate to it :)
Daryl, Dave, thanks for the input and helping me track this down.
F
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
