WebSphere Application Server and the JDBC 4.0 Wrapper Pattern

Resolving The Problem

The following code snippets show how the JDBC 4.0 wrapper pattern can be used to obtain a native Oracle connection or a native Oracle PreparedStatement object:

1. Obtain an oracle.jdbc.OracleConnection:
Context ic = new InitialContext();
DataSource ds = (DataSource)ic.lookup("jdbc/OracleDS");
Connection conn = ds.getConnection();

// Returns true if this either implements the interface argument
// or is directly or indirectly a wrapper for an object that does.
if (conn.isWrapperFor(oracle.jdbc.OracleConnection.class)) {
// Returns an object that implements the given interface to
// allow access to non-standard methods, or standard methods
// not exposed by the proxy.
oracle.jdbc.OracleConnection oraCon = conn.unwrap(oracle.jdbc.OracleConnection.class);
// Do some Oracle-specific work here.
}
conn.close();

2. Obtain an OraclePreparedStatement:
Context ic = new InitialContext();
DataSource ds = (DataSource)ic.lookup("jdbc/OracleDS");
Connection conn = ds.getConnection();

PreparedStatement pstmt = conn.prepareStatement("SELECT 1 FROM DUAL");
if(pstmt.isWrapperFor(oracle.jdbc.OraclePreparedStatement.class)){
oracle.jdbc.OraclePreparedStatement opstmt = pstmt.unwrap(oracle.jdbc.OraclePreparedStatement.class);
// Do some Oracle-specific work here.
}
pstmt.close();
conn.close();