Browse Source

Merge pull request #1204 from marschall:SPR-14809

* pr/1204:
  Remove OracleLobHandler from documentation
pull/1207/head
Stephane Nicoll 9 years ago
parent
commit
6fb4352e5c
  1. 4
      spring-jdbc/src/main/java/org/springframework/jdbc/support/nativejdbc/SimpleNativeJdbcExtractor.java
  2. 2
      src/asciidoc/data-access.adoc

4
spring-jdbc/src/main/java/org/springframework/jdbc/support/nativejdbc/SimpleNativeJdbcExtractor.java

@ -35,10 +35,6 @@ package org.springframework.jdbc.support.nativejdbc; @@ -35,10 +35,6 @@ package org.springframework.jdbc.support.nativejdbc;
* flags to "true". If none of the statement types is wrapped - or you solely need
* Connection unwrapping in the first place -, the defaults are fine.
*
* <p>SimpleNativeJdbcExtractor is a common choice for use with OracleLobHandler, which
* just needs Connection unwrapping via the {@link #getNativeConnectionFromStatement}
* method. This usage will work with almost any connection pool.
*
* <p>For full usage with JdbcTemplate, i.e. to also provide Statement unwrapping:
* <ul>
* <li>Use a default SimpleNativeJdbcExtractor for Resin and SJSAS (no JDBC

2
src/asciidoc/data-access.adoc

@ -3230,7 +3230,7 @@ Sometimes you need to access vendor specific JDBC methods that differ from the s @@ -3230,7 +3230,7 @@ Sometimes you need to access vendor specific JDBC methods that differ from the s
JDBC API. This can be problematic if you are running in an application server or with a
`DataSource` that wraps the `Connection`, `Statement` and `ResultSet` objects with its
own wrapper objects. To gain access to the native objects you can configure your
`JdbcTemplate` or `OracleLobHandler` with a `NativeJdbcExtractor`.
`JdbcTemplate` with a `NativeJdbcExtractor`.
The `NativeJdbcExtractor` comes in a variety of flavors to match your execution
environment:

Loading…
Cancel
Save