Package org.springframework.jdbc.datasource

Class DriverManagerDataSource

java.lang.Object
org.springframework.jdbc.datasource.AbstractDataSource
org.springframework.jdbc.datasource.AbstractDriverBasedDataSource
org.springframework.jdbc.datasource.DriverManagerDataSource
All Implemented Interfaces:
Wrapper, CommonDataSource, DataSource
Direct Known Subclasses:
SingleConnectionDataSource
public class DriverManagerDataSource extends AbstractDriverBasedDataSource
Simple implementation of the standard JDBC 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 a Jakarta 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 Jakarta 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 org.springframework.mock.jndi.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.

Since:
14.03.2003
Author:
Juergen Hoeller
See Also:

  • Constructor Details

    • DriverManagerDataSource

      public DriverManagerDataSource()
      Constructor for bean-style configuration.

    • DriverManagerDataSource

      public DriverManagerDataSource(String url)
      Create a new DriverManagerDataSource with the given JDBC URL, not specifying a username or password for JDBC access.
      Parameters:
      url - the JDBC URL to use for accessing the DriverManager
      See Also:

    • DriverManagerDataSource

      public DriverManagerDataSource(String url, String username, String password)
      Create a new DriverManagerDataSource with the given standard DriverManager parameters.
      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
      See Also:

    • DriverManagerDataSource

      public DriverManagerDataSource(String url, Properties conProps)
      Create a new DriverManagerDataSource with the given JDBC URL, not specifying a username or password for JDBC access.
      Parameters:
      url - the JDBC URL to use for accessing the DriverManager
      conProps - the JDBC connection properties
      See Also:

  • Method Details