19 * Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.
20 *
21 * Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA
22 * or visit www.oracle.com if you need additional information or have any
23 * questions.
24 */
25
26 package javax.sql;
27
28 import java.sql.Connection;
29 import java.sql.SQLException;
30 import java.sql.Wrapper;
31
32 /**
33 * <p>A factory for connections to the physical data source that this
34 * {@code DataSource} object represents. An alternative to the
35 * {@code DriverManager} facility, a {@code DataSource} object
36 * is the preferred means of getting a connection. An object that implements
37 * the {@code DataSource} interface will typically be
38 * registered with a naming service based on the
39 * Java<sup><font size=-2>TM</font></sup> Naming and Directory (JNDI) API.
40 * <P>
41 * The {@code DataSource} interface is implemented by a driver vendor.
42 * There are three types of implementations:
43 * <OL>
44 * <LI>Basic implementation -- produces a standard {@code Connection}
45 * object
46 * <LI>Connection pooling implementation -- produces a {@code Connection}
47 * object that will automatically participate in connection pooling. This
48 * implementation works with a middle-tier connection pooling manager.
49 * <LI>Distributed transaction implementation -- produces a
50 * {@code Connection} object that may be used for distributed
51 * transactions and almost always participates in connection pooling.
52 * This implementation works with a middle-tier
53 * transaction manager and almost always with a connection
54 * pooling manager.
55 * </OL>
56 * <P>
57 * A {@code DataSource} object has properties that can be modified
58 * when necessary. For example, if the data source is moved to a different
59 * server, the property for the server can be changed. The benefit is that
|
19 * Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.
20 *
21 * Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA
22 * or visit www.oracle.com if you need additional information or have any
23 * questions.
24 */
25
26 package javax.sql;
27
28 import java.sql.Connection;
29 import java.sql.SQLException;
30 import java.sql.Wrapper;
31
32 /**
33 * <p>A factory for connections to the physical data source that this
34 * {@code DataSource} object represents. An alternative to the
35 * {@code DriverManager} facility, a {@code DataSource} object
36 * is the preferred means of getting a connection. An object that implements
37 * the {@code DataSource} interface will typically be
38 * registered with a naming service based on the
39 * Java™ Naming and Directory (JNDI) API.
40 * <P>
41 * The {@code DataSource} interface is implemented by a driver vendor.
42 * There are three types of implementations:
43 * <OL>
44 * <LI>Basic implementation -- produces a standard {@code Connection}
45 * object
46 * <LI>Connection pooling implementation -- produces a {@code Connection}
47 * object that will automatically participate in connection pooling. This
48 * implementation works with a middle-tier connection pooling manager.
49 * <LI>Distributed transaction implementation -- produces a
50 * {@code Connection} object that may be used for distributed
51 * transactions and almost always participates in connection pooling.
52 * This implementation works with a middle-tier
53 * transaction manager and almost always with a connection
54 * pooling manager.
55 * </OL>
56 * <P>
57 * A {@code DataSource} object has properties that can be modified
58 * when necessary. For example, if the data source is moved to a different
59 * server, the property for the server can be changed. The benefit is that
|