Re: Cloning EO's in Java

[Stuart MacKay]

Holger Hoffstaette wrote:

> Am I making sense? If not, don't hesitate to ask again.

Perfect sense however the EO was being used as an object and not as the key when it was added to the dictionary:

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

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.

The other workaround is to set the lastModifiedBy relationship at the last minute (for the list of inserted and updated objects obtained from the WODisplayGroup) when the changes are to be saved, however I'd prefer the default value route as it's is more elegant.

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.

Thanks for the insights however.

Stuart