A. Abram White 1c8f82b810 Move LockManager API back to using int timeouts, since that's the way they're ... handled elsewhere (FetchConfiguration, Broker, etc). Only use the lock timeout on a forUpdate query if it is greater than the configured query timeout. Selects that are made *only* to lock a row (rather than to query data, with locking as a side effect) still use the lock timeout exclusively, ignoring the query timeout. git-svn-id: https://svn.apache.org/repos/asf/incubator/openjpa/trunk@526192 13f79535-47bb-0310-9956-ffa450edef68		2007-04-06 15:08:39 +00:00
..
src/main	Move LockManager API back to using int timeouts, since that's the way they're	2007-04-06 15:08:39 +00:00
pom.xml	Updated to version 0.9.7-incubating-SNAPSHOT	2006-11-12 22:28:45 +00:00