-Donald
In looking at adding query timeout support for JPA 2.0, I've discovered
that the existing lock manager code is using setQueryTimeout() for the
locks, instead of using the server-side methods (like for DB2 "SET LOCK
TIMEOUT <secs>".) What is the suggested way of creating a
"compatibility" mode, so users can choose the old behavior over the new
2.0 implementation?
- How to support previous non-spec behavior compatibility Donald Woods
