In some cases, jOOQ needs to get access to the native JDBC driver APIs in
order to call vendor specific methods, such as Oracle's
OracleConnection.createARRAY(). jOOQ doesn't expect clients to
provide a native JDBC
Connection through the
ConnectionProvider SPI. Implementations may well provide jOOQ with
some proxy that implements things like logging, thread-bound
transactionality, connection pooling, etc.
In order to access the native API,
Wrapper.unwrap(Class) needs to be
called, or in some cases, when third party libraries do not properly
implement this contract, some specific methods are called reflectively,
Not all such third party libraries are "known" to jOOQ, so clients can implement their own unwrapper to support theirs.
- Lukas Eder