Just want to make sure we are doing this correctly...

1. We want to load an object
2. Update the object in another layer in a browser. (disconnected)
3. Come back and reassociate the object with a Session and use saveOrUpdate to commit the new changes and updates.

Question: Is session.lock(foo, LockMode.NONE) the same as reassociating the transient object with a new session without doing selects/reads from the database?

I just want to make sure that there is nothing else that is going on here (with session.lock with LockMode.NONE). We are using Timestamps for optimisitic locking strategy since our environment is not highly concurrent on the records we are working with and should suffice.

Is there a better way to reassociate the object with a new Session. If this is the way to do this then I think that the API should be updated with session.reassociate(Object o). This would be a wrapper for the above session.lock method which seems like a confusing name for what is happening.

Thanks,

Mark
[code][/code]

LockMode.NONE: Don't go to the database unless the object is not in either cache.

LockMode.READ: Bypass both levels of the cache and perform a version check, to verify that the object is the same version that currently exists in the database.

The others are pessimistic and exclusive locks for the duration of the transaction on that object.