Roel De Nijs wrote:If you don't send a lockCookie to the update-method (or you send always 0) how are you able to guarantee that the record you want to update is locked by the same client which wants to update the record?
As far as I know this is how the required interface should work and if you break these requirements (which you do based on your explanation), you'll fail automatically.
Roel De Nijs wrote:
In the snippet you provided, you pass 0l to the update-method. That's not according to how your locking mechanism should work (but this could be a typo you made).
Roel De Nijs wrote:And did you add logic to your business service to prevent double bookings?
John Oconnor wrote:if not throws a exception (exception declared in DB)