Thanks David.
I can see the attribute enable-lock on the entity. Do I just set this
to true
David E Jones wrote:
This is usually referred to as an "optimistic lock", and yes this can be turned on
per-entity in the entity definition itself. In some cases logic and UI changes will be necessary to
support this, ie in order to support passing the timestamp that represents the "version"
of the record to make sure it is the same when saving the changes.
-David
On Jan 6, 2010, at 9:56 AM, Christopher Snow wrote:
I have just done a quick test and it appears that if two users are editing and
save the same record, the last save wins. Is it possible to change this
behavior to throw an error if the data is stale, like hibernate's
StaleObjectStateException?
Many thanks,
Chris
--
Chris Snow - CEng MBCS CITP MBA (Tech Mgmt) (Open) CISSP
Tel: 01453 890660
Mob: 07944 880950
Www: www.snowconsulting.co.uk
