/*
 * Copyright (c) 2000, 2013, Oracle and/or its affiliates. All rights reserved.
 * ORACLE PROPRIETARY/CONFIDENTIAL. Use is subject to license terms.
 *
 *
 *
 *
 *
 *
 *
 *
 *
 *
 *
 *
 *
 *
 *
 *
 *
 *
 *
 *
 */

package javax.sql;

import java.sql.Connection;
import java.sql.SQLException;
import java.sql.Wrapper;

/**
 * <p>A factory for connections to the physical data source that this
 * {@code DataSource} object represents. An alternative to the
 * {@code DriverManager} facility, a {@code DataSource} object
 * is the preferred means of getting a connection. An object that implements
 * the {@code DataSource} interface will typically be
 * registered with a naming service based on the
 * Java&trade; Naming and Directory (JNDI) API.
 * <P>
 * The {@code DataSource} interface is implemented by a driver vendor.
 * There are three types of implementations:
 * <OL>
 * <LI>Basic implementation -- produces a standard {@code Connection}
 * object
 * <LI>Connection pooling implementation -- produces a {@code Connection}
 * object that will automatically participate in connection pooling. This
 * implementation works with a middle-tier connection pooling manager.
 * <LI>Distributed transaction implementation -- produces a
 * {@code Connection} object that may be used for distributed
 * transactions and almost always participates in connection pooling.
 * This implementation works with a middle-tier
 * transaction manager and almost always with a connection
 * pooling manager.
 * </OL>
 * <P>
 * A {@code DataSource} object has properties that can be modified
 * when necessary. For example, if the data source is moved to a different
 * server, the property for the server can be changed. The benefit is that
 * because the data source's properties can be changed, any code accessing
 * that data source does not need to be changed.
 * <P>
 * A driver that is accessed via a {@code DataSource} object does not
 * register itself with the {@code DriverManager}. Rather, a
 * {@code DataSource} object is retrieved though a lookup operation
 * and then used to create a {@code Connection} object. With a basic
 * implementation, the connection obtained through a {@code DataSource}
 * object is identical to a connection obtained through the
 * {@code DriverManager} facility.
 * <p>
 * An implementation of {@code DataSource} must include a public no-arg
 * constructor.
 *
 * @since 1.4
 */

public interface DataSource extends CommonDataSource, Wrapper {

 /**
 * <p>Attempts to establish a connection with the data source that
 * this {@code DataSource} object represents.
 *
 * @return a connection to the data source
 * @exception SQLException if a database access error occurs
 * @throws java.sql.SQLTimeoutException when the driver has determined that the
 * timeout value specified by the {@code setLoginTimeout} method
 * has been exceeded and has at least tried to cancel the
 * current database connection attempt
 */
 Connection getConnection() throws SQLException;

 /**
 * <p>Attempts to establish a connection with the data source that
 * this {@code DataSource} object represents.
 *
 * @param username the database user on whose behalf the connection is
 * being made
 * @param password the user's password
 * @return a connection to the data source
 * @exception SQLException if a database access error occurs
 * @throws java.sql.SQLTimeoutException when the driver has determined that the
 * timeout value specified by the {@code setLoginTimeout} method
 * has been exceeded and has at least tried to cancel the
 * current database connection attempt
 * @since 1.4
 */
 Connection getConnection(String username, String password)
 throws SQLException;
}