Skip to content

Commit

Permalink
Merge pull request #1204 from marschall:SPR-14809
Browse files Browse the repository at this point in the history
* pr/1204:
  Remove OracleLobHandler from documentation
  • Loading branch information
snicoll committed Oct 14, 2016
2 parents 960cc42 + eee742d commit 6fb4352
Show file tree
Hide file tree
Showing 2 changed files with 1 addition and 5 deletions.
Expand Up @@ -35,10 +35,6 @@
* 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
Expand Down
2 changes: 1 addition & 1 deletion src/asciidoc/data-access.adoc
Expand Up @@ -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:
Expand Down

0 comments on commit 6fb4352

Please sign in to comment.