I am also seeing the same problem. db.update tries to create the previously existing object and fails with a DuplicateIdentityException.
-- Don -----Original Message----- From: Edwin van Stam [mailto:[EMAIL PROTECTED]] Sent: Friday, March 22, 2002 12:04 PM To: [EMAIL PROTECTED] Subject: [castor-dev] Many-to-Many Persistence Problems Hello, The solution with the setAutoStore() method of Don was very helpfull. I was wondering if anyone also knows how to tackle the situation in which autoStore=true, and the object to be stored contains references to other objects, some of which are already persistent and some are new instances. If autoStore=true a DuplicateIdentityException occurs on the objects that are already persistent. Castor tries to create these again. If autoStore=false, no exception occurs, but the transient objects are not stored. Thx, Edwin -- **************************************************************************** This message contains information that may be privileged or confidential and is the property of the Cap Gemini Ernst & Young Group. It is only intended for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. **************************************************************************** ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
