InfoCenter Home >
3: Migration overview >
3.3: Migrating APIs and specifications >
3.3.8: Migrating to supported database connection APIs (and JDBC)

3.3.8: Migrating to supported database connection APIs (and JDBC)

Connection pooling (provided through DataSource objects) was introduced in IBM WebSphere Application Server Version 3.0x. Applications that use Version 3.0x connection pooling need to be changed slightly and recompiled.

If existing applications are still using the connection manager model from Version 2.0x, you must update the application code to use the current connection pooling model (see the Related information). The shift in models corresponds to a change in supported JDBC specification levels.

ConnectionPreemptedException, introduced in Version 3.0x, no longer exists. StaleConnectionException has replaced ConnectionPremptedException in all cases. For details, see the Related information.

Items newly deprecated in Version 4.0

The packages com.ibm.db2.jdbc.app.stdext.javax.sql and com.ibm.ejs.dbm.jdbcext have been deprecated. Applications using the com.ibm.ejs.dbm.jdbcext package will still be allowed to retrieve a datasource, but new datasources cannot be created or bound into JNDI by using this interface. All new datasources must be created by using com.ibm.websphere.advanced.cm.factory.DataSourceFactory.

The following methods in com.ibm.websphere.advanced.cm.factory.DataSourceFactory have been deprecated: createJTADataSource() and createJDBCDataSource(). These methods have been replaced with the getDataSource(java.util.Properties) method.

The class com.ibm.ejs.cm.portability.StaleConnectionException has been deprecated. Applications currently using this class will still function, but it is recommended that new applications be written using com.ibm.websphere.ce.cm.StaleConnectionException.

Go to previous article: Migrating to supported security APIs Go to next article: Migrating from the Version 3.0x connection pooling model

 

 
Go to previous article: Migrating to supported security APIs Go to next article: Migrating from the Version 3.0x connection pooling model