> > session.lock(website, LockMode.NONE); The problem may also be with some (eagerly or immediately loaded) associated object. This can make NonUniqueObjectExceptions quite nasty: let's say you have a detached A referencing a detached B, then, in a new Session you load C which also references B. you try to lock B (and the object-graph attached to it) and bang.
> > What pattern are you using for your hibernate sessions? > Session per thread? > Long Session? Etc. if he'd use long session, he wouldn't have the problem ;-), really! See the previous thread on that, or: http://marcus-schulte.blogspot.com/2005/04/if-you-cant-hide-it-below-hide-it .html. regards, Marcus --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
