public class DriverManagerDataSource extends AbstractDriverBasedDataSource
DataSource interface,
configuring the plain old JDBC DriverManager via bean properties, and
returning a new Connection from every getConnection call.
NOTE: This class is not an actual connection pool; it does not actually pool Connections. It just serves as simple replacement for a full-blown connection pool, implementing the same standard interface, but creating new Connections on every call.
Useful for test or standalone environments outside of a Java EE container, either
as a DataSource bean in a corresponding ApplicationContext or in conjunction with
a simple JNDI environment. Pool-assuming Connection.close() calls will
simply close the Connection, so any DataSource-aware persistence code should work.
NOTE: Within special class loading environments such as OSGi, this class
is effectively superseded by SimpleDriverDataSource due to general class
loading issues with the JDBC DriverManager that be resolved through direct Driver
usage (which is exactly what SimpleDriverDataSource does).
In a Java EE container, it is recommended to use a JNDI DataSource provided by
the container. Such a DataSource can be exposed as a DataSource bean in a Spring
ApplicationContext via JndiObjectFactoryBean,
for seamless switching to and from a local DataSource bean like this class.
For tests, you can then either set up a mock JNDI environment through Spring's
SimpleNamingContextBuilder, or switch the
bean definition to a local DataSource (which is simpler and thus recommended).
This DriverManagerDataSource class was originally designed alongside
Apache Commons DBCP
and C3P0, featuring bean-style
BasicDataSource/ComboPooledDataSource classes with configuration
properties for local resource setups. For a modern JDBC connection pool, consider
HikariCP instead,
exposing a corresponding HikariDataSource instance to the application.
SimpleDriverDataSourcelogger| Constructor and Description |
|---|
DriverManagerDataSource()
Constructor for bean-style configuration.
|
DriverManagerDataSource(String url)
Create a new DriverManagerDataSource with the given JDBC URL,
not specifying a username or password for JDBC access.
|
DriverManagerDataSource(String url,
Properties conProps)
Create a new DriverManagerDataSource with the given JDBC URL,
not specifying a username or password for JDBC access.
|
DriverManagerDataSource(String url,
String username,
String password)
Create a new DriverManagerDataSource with the given standard
DriverManager parameters.
|
| Modifier and Type | Method and Description |
|---|---|
protected Connection |
getConnectionFromDriver(Properties props)
Obtain a Connection using the given properties.
|
protected Connection |
getConnectionFromDriverManager(String url,
Properties props)
Getting a Connection using the nasty static from DriverManager is extracted
into a protected method to allow for easy unit testing.
|
void |
setDriverClassName(String driverClassName)
Set the JDBC driver class name.
|
getCatalog, getConnection, getConnection, getConnectionFromDriver, getConnectionProperties, getPassword, getSchema, getUrl, getUsername, setCatalog, setConnectionProperties, setPassword, setSchema, setUrl, setUsernamegetLoginTimeout, getLogWriter, getParentLogger, isWrapperFor, setLoginTimeout, setLogWriter, unwrappublic DriverManagerDataSource()
public DriverManagerDataSource(String url)
url - the JDBC URL to use for accessing the DriverManagerDriverManager.getConnection(String)public DriverManagerDataSource(String url, String username, String password)
url - the JDBC URL to use for accessing the DriverManagerusername - the JDBC username to use for accessing the DriverManagerpassword - the JDBC password to use for accessing the DriverManagerDriverManager.getConnection(String, String, String)public DriverManagerDataSource(String url, Properties conProps)
url - the JDBC URL to use for accessing the DriverManagerconProps - the JDBC connection propertiesDriverManager.getConnection(String)public void setDriverClassName(String driverClassName)
NOTE: DriverManagerDataSource is primarily intended for accessing
pre-registered JDBC drivers. If you need to register a new driver,
consider using SimpleDriverDataSource instead. Alternatively, consider
initializing the JDBC driver yourself before instantiating this DataSource.
The "driverClassName" property is mainly preserved for backwards compatibility,
as well as for migrating between Commons DBCP and this DataSource.
protected Connection getConnectionFromDriver(Properties props) throws SQLException
AbstractDriverBasedDataSourceTemplate method to be implemented by subclasses.
getConnectionFromDriver in class AbstractDriverBasedDataSourceprops - the merged connection propertiesSQLException - in case of failureprotected Connection getConnectionFromDriverManager(String url, Properties props) throws SQLException
SQLExceptionDriverManager.getConnection(String, java.util.Properties)