root
/
spring-framework
mirror of https://github.com/spring-projects/spring-framework.git
1
0
Fork 0
Code Issues Actions 6 Packages Projects Releases Wiki Activity

Remove OracleLobHandler from documentation 

Now that OracleLobHandler has finally been removed it should also be
removed from the documentation.

This commit includes the following changes:

 * remove OracleLobHandler references from Javadoc
 * remove OracleLobHandler references from Asciidoctor

Issue: SPR-14809
Closes gh-1204
This commit is contained in:
Philippe Marschall 2016-10-14 15:45:16 +02:00 committed by Stephane Nicoll
parent 960cc42060
commit eee742da7f
2 changed files with 1 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -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 * 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. * 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: * <p>For full usage with JdbcTemplate, i.e. to also provide Statement unwrapping:
* <ul> * <ul>
* <li>Use a default SimpleNativeJdbcExtractor for Resin and SJSAS (no JDBC * <li>Use a default SimpleNativeJdbcExtractor for Resin and SJSAS (no JDBC

2
src/asciidoc/data-access.adoc
View File

@ -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 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 `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 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 The `NativeJdbcExtractor` comes in a variety of flavors to match your execution
environment: environment: