I've got an Eclipse RCP that commits changes to the database after an object has been edited. So when a user wishes to delete an object it gets deleted from the database immediately. If the user now uses the redo function, the object is restored and will be saved. Well that is the problem: This object already has an ID, so EclipseLink throws an OptimisticLockException and says "the object cannot be merged because it has changed or been deleted since it was last read".
Is there an option to force Eclipselink to ignore the ID? Since I'm using Texo to persist the objects, I cannot influence EclipseLink to use persist or merge.