I notices my changes were not being persisted to the database, and when I took away this call (right before the sess.update):

sess.lock(inObj, LockMode.NONE);

..my changes started persisting again. Could someone explain to me when this is needed, and when it is not? I causes a lot of confusion at home/work. Should we not be using it? Sometimes if we dont we get TransientObject exceptions... Thanks for any explanation.

Matt Dowell

This call basically only reattaches a detached instance with the Session. The object can be modified after lock() and changes will be saved. However, you shouldn't have changed the detached instance while it wasn't associated with the Session.

If you manipulated the detached object, use update() to reassociate it with a new Session. Using both lock() and update() to reattach doesn't make much sense.