Example usage for org.springframework.jdbc.datasource DelegatingDataSource subclass-usage

List of usage examples for org.springframework.jdbc.datasource DelegatingDataSource subclass-usage

Introduction

In this page you can find the example usage for org.springframework.jdbc.datasource DelegatingDataSource subclass-usage.

Usage

From source file ome.services.db.SelfCorrectingDataSource.java

/**
 * {@link DataSource} delegate which wraps the
 */
public class SelfCorrectingDataSource extends DelegatingDataSource {

    private final static Log log = LogFactory.getLog(SelfCorrectingDataSource.class);

From source file com.gu.management.database.logging.LoggingDataSource.java

public class LoggingDataSource extends DelegatingDataSource {

    private static final Logger LOG = Logger.getLogger(LoggingDataSource.class);

    private final PreparedStatementProxyFactory preparedStatementProxyFactory;

From source file com.jolbox.bonecp.spring.DynamicDataSourceProxy.java

/** Like a normal datasource except it supports an extra method: switchDataSource to slowly migrate to a new datasource.
 * 
 * Simply call switchDataSource with your new BoneCP configuration: the existing pool will be shutdown gracefully (checkout out
 * connections are unaffected) and a new one will take it's place. A typical use case would be to transparently instruct your application
 * to use a new database without restarting the application.
 *   

From source file org.cfr.capsicum.datasource.TransactionAwareDataSourceProxy.java

/**
 * Proxy for a target JDBC {@link javax.sql.DataSource}, adding awareness of
 * Spring-managed transactions. Similar to a transactional JNDI DataSource
 * as provided by a J2EE server.
 *
 * <p>Data access code that should remain unaware of Spring's data access support

From source file org.springframework.jdbc.datasource.LazyConnectionDataSourceProxy.java

/**
 * Proxy for a target DataSource, fetching actual JDBC Connections lazily,
 * i.e. not until first creation of a Statement. Connection initialization
 * properties like auto-commit mode, transaction isolation and read-only mode
 * will be kept and applied to the actual JDBC Connection as soon as an
 * actual Connection is fetched (if ever). Consequently, commit and rollback

From source file com.mtgi.analytics.sql.BehaviorTrackingDataSource.java

/**
 * A datasource which adds SQL event logging to the behavior tracking database.  Events are persisted
 * to the required {@link #setTrackingManager(BehaviorTrackingManager) BehaviorTrackingManager}.  Events
 * are of type "jdbc" unless overridden with a call to {@link #setEventType(String)}.  Event names are the
 * Statement API call that executed the SQL (e.g. "execute", "executeQuery", "executeUpdate"), with event
 * data containing the exact SQL and parameter values logged.