0 Replies Latest reply on Oct 2, 2003 3:13 PM by senthilcool

    Commit option A and optimistic offline locking

    senthilcool Newbie

      Is there a way to do optimistic offline locking with commit option A. i.e, whenever the bean is to be updated, is there a way to reload a timestamp field from the database and verify it against the value sent from the client to see if it has been modified ?