0

I am trying to implement optimistic locking using JPA. I read that adding one additional field, version with @Version annotation can used to apply implicit optimistic locking. After implementing, I will be able to prevent lost updates in case of multiple users trying to update the same entity.If any update is made and if version field do not match with the version field of entity, meaning entity was updated meanwhile by other user, then no row is updated, thereby preventing lost update.

I am using Spring Transaction management support where for updating entity, all I have to is update the Entity fields and database update is taken care by Spring transaction manager, meaning I need not call update query explicitly.

My Question is that, How would I be able to know if update made for a particular user was successful?

Md Zahid Raza
  • 941
  • 1
  • 11
  • 28

1 Answers1

0

OptimisticLockException will be thrown if an operation was unsuccessful - if other transaction has modified entity before. Related threads for more details:

Community
  • 1
  • 1
Justinas Jakavonis
  • 8,220
  • 10
  • 69
  • 114
  • Thanks for response. Yes, OLE exception will be thrown. But my question was, as I am trying to use Spring Transaction management, So I do not execute update or commit explicitly. So, How can I catch this exception and take appropriate action? – Md Zahid Raza Aug 20 '16 at 13:21
  • According to http://stackoverflow.com/questions/17203452/how-to-catch-optimisticlockexception-in-jpa it can be handled outside invoked method or call entityManager.flush() explicitly inside. – Justinas Jakavonis Aug 22 '16 at 12:57