hi,

when i try to use saveOrUpdateCopy, i've been getting a lazy initialization exception. the object that i'm trying to create has been added to a parent's collection which was loaded in another session. how can i correct this error, do i have to manually associate the parent object to the session with this method?

thanks, cam

Ummm ... this should probably not happen. You might want to submit a simplified test case to JIRA. Not sure why you would observe this.

well, i've been having some trouble from a system design point of view and this seemed like a solution until i fully understood what it actually did. what i was really looking for was a saveOrUpdateClone method, or such like. mabye i should explain what i'm trying to accomplish.

i have a wizard which populates an object with primitive values and parent objects. i then attempt to save the object, but if an error occurs i want to try to save the same object again after modifying any offending values or whatever. the problem is that once the object gets passed into the session for the save, it gets assigned an identifier so if i try to save the object again i'll get a error. i had considered just reseting the identifier, but have no way of differentiating between unsaved objects with an identifier, or persisted objects.

so, the reason i was looking at the saveOrUpdateCopy was so that i could attmpt to save a clone of the object so that if it failed i could just re-edit the original and then pass in another clone. like i said, i found out that this isn't what this method does anyway, but i still want to pursue this (prospective) solution.

this has taken a wide step away from hibernate, but what can you recommend i do? i don't really want to have to recreate and repopulate a new object on each attempt. i know this senario probably wont crop up often with lots of validation etc, but i'd like to have the design for it instead of making the user re-enter all the data in the wizard again.

thanks cam

ps. will submit the test i was using to jira