Just a ME-TOO
We do exactly the same -- use JBoss/J2EE transactions within the middle-tier,
but also have a lockVersion field in the VO sent to the client -- so when the
client hits save -- we lookup the entity - compare the lockVersion with that in
the VO and if they don't match we throw a
Thanks,
I had looked at your post and you are right the transaction must be
atomized for JBoss optimistic locking to work. My application writers are
adverse to handling their own transactions. I am going to have to
declaratively setup which field in a table is to be checked for
Hi,
I am not an expert in the area but I had the same problem a few
days ago. Your XML configuration seems ok to me.
What you need to make sure for optimistic locking to work
is to include the read of the record, the user edit time, and the update
of the record into one single transaction.
The
