java.lang.Object | |||
↳ | org.springframework.jdbc.datasource.AbstractDataSource | ||
↳ | org.springframework.jdbc.datasource.AbstractDriverBasedDataSource | ||
↳ | org.springframework.jdbc.datasource.DriverManagerDataSource |
Known Direct Subclasses |
Simple implementation of the standard JDBC javax.sql.DataSource interface,
configuring the plain old JDBC java.sql.DriverManager via bean properties, and
returning a new java.sql.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 J2EE 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 J2EE 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).
If you need a "real" connection pool outside of a J2EE container, consider Apache's Jakarta Commons DBCP or C3P0. Commons DBCP's BasicDataSource and C3P0's ComboPooledDataSource are full connection pool beans, supporting the same basic properties as this class plus specific settings (such as minimal/maximal pool size etc).
[Expand]
Inherited Fields | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
From class
org.springframework.jdbc.datasource.AbstractDataSource
|
Public Constructors | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Constructor for bean-style configuration.
| |||||||||||
Create a new DriverManagerDataSource with the given JDBC URL,
not specifying a username or password for JDBC access.
| |||||||||||
Create a new DriverManagerDataSource with the given standard
DriverManager parameters.
| |||||||||||
Create a new DriverManagerDataSource with the given JDBC URL,
not specifying a username or password for JDBC access.
| |||||||||||
This constructor is deprecated.
since Spring 2.5. DriverManagerDataSource is primarily
intended for accessing pre-registered JDBC drivers.
If you need to register a new driver, consider using
SimpleDriverDataSource instead.
|
Public Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Set the JDBC driver class name.
|
Protected Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Obtain a Connection using the given properties.
| |||||||||||
Getting a Connection using the nasty static from DriverManager is extracted
into a protected method to allow for easy unit testing.
|
[Expand]
Inherited Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
From class
org.springframework.jdbc.datasource.AbstractDriverBasedDataSource
| |||||||||||
From class
org.springframework.jdbc.datasource.AbstractDataSource
| |||||||||||
From class
java.lang.Object
| |||||||||||
From interface
java.sql.Wrapper
| |||||||||||
From interface
javax.sql.CommonDataSource
| |||||||||||
From interface
javax.sql.DataSource
|
Constructor for bean-style configuration.
Create a new DriverManagerDataSource with the given JDBC URL, not specifying a username or password for JDBC access.
url | the JDBC URL to use for accessing the DriverManager |
---|
Create a new DriverManagerDataSource with the given standard DriverManager parameters.
url | the JDBC URL to use for accessing the DriverManager |
---|---|
username | the JDBC username to use for accessing the DriverManager |
password | the JDBC password to use for accessing the DriverManager |
Create a new DriverManagerDataSource with the given JDBC URL, not specifying a username or password for JDBC access.
url | the JDBC URL to use for accessing the DriverManager |
---|---|
conProps | JDBC connection properties |
This constructor is deprecated.
since Spring 2.5. DriverManagerDataSource is primarily
intended for accessing pre-registered JDBC drivers.
If you need to register a new driver, consider using
SimpleDriverDataSource
instead.
Create a new DriverManagerDataSource with the given standard DriverManager parameters.
driverClassName | the JDBC driver class name |
---|---|
url | the JDBC URL to use for accessing the DriverManager |
username | the JDBC username to use for accessing the DriverManager |
password | the JDBC password to use for accessing the DriverManager |
Set the JDBC driver class name. This driver will get initialized on startup, registering itself with the JDK's DriverManager.
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.
Obtain a Connection using the given properties.
Template method to be implemented by subclasses.
props | the merged connection properties |
---|
SQLException |
---|
Getting a Connection using the nasty static from DriverManager is extracted into a protected method to allow for easy unit testing.
SQLException |
---|