Re: Cloning EO's in Java

[Holger Hoffstaette]

>Perfect sense however the EO was being used as an object and not as the key

>when it was added to the dictionary:

Aargh..

>[defaultValues setObject:[[self session] login] forKey:@"lastModifiedBy"];

That should work fine. I think I remember reading that the Java docs
mistakenly switched the args key/value order, so there's the possibility
that you want to do the right thing, but accidentally call the method with
the args in order wrong the. This might be Yoda's way of telling you to use
Objective-C. :)

>If copyWithZone with [self retain] would that generate side effects with
>other parts of EOF since EO's are typically mutable and implementing
>copyWithZone as above conceptually goes against that.

Probably not, I've used that and it works fine. Just don't start to
arbitrarily copy EOs and expect different instances..

>The reason I asked about the copyWithZone: question is that this has come up
>several times in the archive, in slightly different circumstances and as yet
>I haven't seen a cogent explanation of why the exception is thrown, given
>there might be a common root cause.

No, your code should work. I do not have the original Java fragment
anymore, but I'm reasonably sure you've just accidentally confused the
arguments. Or the Java bridge does something funny (which I doubt in this
case).

good luck
Holger