lock() and tryLock() behavior in OJB 1.0.4

I was wondering what the behavior was when obtaining a WRITE lock on an
object using the ODMG APIs in OJB 1.0.4.  I expected that this call
would reload the object from the database if there had been any changes
commited before obtaining the WRITE lock.  This doesn't seem to be the
case in the code I'm running, but maybe there's something wrong in my
configuration.
 
I'm using LockManagerInMemoryImpl, isolation level for all objects are
set to uncommited-read, and LockAssociations=READ.   Is there something
else I might be missing here?
 
Thanks,
Phil