we are finding that we need implement the clone method on our objects that are persisted because hiberante keeps some kind of magic connection to the actual object reference. we want to be able to rid a given object instance of ANY reference to hiberante, so we can just blank out the id's and resave it, and it will save as a new object. our current solution is to implement the clone() method on all our persistant objects.

If your object does not contain collection, simply session.evict(object) will be enough, no need to override the clone method.

ok, thats a start. suppose it does contain a colllection (which it does, several infact).. do i traverse the object tree and call evict on all child object lists?

thanks
G

Because of the dettach and lazy collection capability, Hibernate set its own impelmentation of collection, so I guess you'll have to copy it manually if you need to be "clean" as you said. But unless you have a remote client and obsolutly don't want the hibernate jar on the client side, I've never found a good reason to clone.

Emmanuel:

It seems Gavin thinks collection item can be evicted by cacade=all.

http://forum.hibernate.org/viewtopic.ph ... ct+cascade

Is that true?

Thanks,

J

It is in my experience.

Really? Please take a quick look at this thread. Do I miss anything? Can you post your sample code and mapping file?

http://forum.hibernate.org/viewtopic.ph ... collection

Thanks,

J

You may want to check out beanlib for arbitrary cloning of the Hibernate entity object graph:
http://hansonchar.blogspot.com/2005/06/ ... rnate.html