- All Known Implementing Classes:
public interface LockingStrategyA strategy abstraction for how locks are obtained in the underlying database.
All locking provided implementations assume the underlying database supports (and that the connection is in) at least read-committed transaction isolation. The most glaring exclusion to this is HSQLDB which only offers support for READ_UNCOMMITTED isolation.
All Methods Instance Methods Abstract Methods Modifier and Type Method Description
lock(Object id, Object version, Object object, int timeout, EventSource session)Acquire an appropriate type of lock on the underlying data that will endure until the end of the current transaction.
void lock(Object id, Object version, Object object, int timeout, EventSource session) throws StaleObjectStateException, LockingStrategyException
id- The id of the row to be locked
version- The current version (or null if not versioned)
object- The object logically being locked (currently not used)
timeout- timeout in milliseconds, 0 = no wait, -1 = wait indefinitely
session- The session from which the lock request originated
StaleObjectStateException- Indicates an inability to locate the database row as part of acquiring the requested lock.
LockingStrategyException- Indicates a failure in the lock attempt