Interface that defines the methods which are common between
An object that registers to be notified of events generated by a
A factory for
A factory for connections to the physical data source that this
An object that provides hooks for connection pool management.
The interface that adds support to the JDBC API for the JavaBeans™ component model.
The interface that a
An interface that must be implemented by a component that wants to be notified when a significant event happens in the life of a
An object that contains information about the columns in a
The facility that a disconnected
An object that implements the
An object that registers to be notified of events that occur on PreparedStatements that are in the Statement pool.
An object that provides support for distributed transactions.
A factory for
java.sqlpackage and, as of the version 1.4 release, is included in the Java Platform, Standard Edition (Java SETM). It remains an essential part of the Java Platform, Enterprise Edition (Java EETM).
javax.sql package provides for the following:
DataSourceinterface as an alternative to the
DriverManagerfor establishing a connection with a data source
Applications use the
APIs directly, but the connection pooling and distributed transaction
APIs are used internally by the middle-tier infrastructure.
DataSourceObject to Make a Connection
javax.sqlpackage provides the preferred way to make a connection with a data source. The
DriverManagerclass, the original mechanism, is still valid, and code using it will continue to run. However, the newer
DataSourcemechanism is preferred because it offers many advantages over the
These are the main advantages of using a
DataSource object to
make a connection:
DataSourceobject that is implemented to work with the middle-tier infrastructure. Connections made through the
DriverManagerdo not have connection and statement pooling or distributed transaction capabilities.
Driver vendors provide
DataSource implementations. A
DataSource object represents a particular
physical data source, and each connection the
creates is a connection to that physical data source.
A logical name for the data source is registered with a naming service that
uses the Java Naming and Directory InterfaceTM
(JNDI) API, usually by a system administrator or someone performing the
duties of a system administrator. An application can retrieve the
DataSource object it wants by doing a lookup on the logical
name that has been registered for it. The application can then use the
DataSource object to create a connection to the physical data
source it represents.
DataSource object can be implemented to work with the
middle tier infrastructure so that the connections it produces will be
pooled for reuse. An application that uses such a
implementation will automatically get a connection that participates in
DataSource object can also be implemented to work with the
middle tier infrastructure so that the connections it produces can be
used for distributed transactions without any special coding.
DataSourceobject that is implemented to work with a middle tier connection pool manager will participate in connection pooling. This can improve performance dramatically because creating new connections is very expensive. Connection pooling allows a connection to be used and reused, thus cutting down substantially on the number of new connections that need to be created.
Connection pooling is totally transparent. It is done automatically
in the middle tier of a Java EE configuration, so from an application's
viewpoint, no change in code is required. An application simply uses
DataSource.getConnection method to get the pooled
connection and uses it the same way it uses any
The classes and interfaces used for connection pooling are:
ConnectionPoolDataSourceobject is called on to create a
PooledConnectionobject, the connection pool manager will register as a
ConnectionEventListenerobject with the new
PooledConnectionobject. When the connection is closed or there is an error, the connection pool manager (being a listener) gets a notification that includes a
If the connection pool manager supports
Statement pooling, for
PreparedStatements, which can be determined by invoking the method
connection pool manager will register as a
object with the new
PooledConnection object. When the
PreparedStatement is closed or there is an error, the connection
pool manager (being a listener)
gets a notification that includes a
DataSourceobject that is implemented to work with the middle tier infrastructure may participate in distributed transactions. This gives an application the ability to involve data sources on multiple servers in a single transaction.
The classes and interfaces used for distributed transactions are:
XAConnection interface is derived from the
PooledConnection interface, so what applies to a pooled connection
also applies to a connection that is part of a distributed transaction.
A transaction manager in the middle tier handles everything transparently.
The only change in application code is that an application cannot do anything
that would interfere with the transaction manager's handling of the transaction.
Specifically, an application cannot call the methods
Connection.rollback, and it cannot set the connection to be in
auto-commit mode (that is, it cannot call
An application does not need to do anything special to participate in a
It simply creates connections to the data sources it wants to use via
DataSource.getConnection method, just as it normally does.
The transaction manager manages the transaction behind the scenes. The
XADataSource interface creates
XAConnection objects, and
XAConnection object creates an
that the transaction manager uses to manage the connection.
RowSetinterface works with various other classes and interfaces behind the scenes. These can be grouped into three categories.
RowSetobject is a JavaBeansTM component because it has properties and participates in the JavaBeans event notification mechanism. The
RowSetListenerinterface is implemented by a component that wants to be notified about events that occur to a particular
RowSetobject. Such a component registers itself as a listener with a rowset via the
RowSet object changes one of its rows, changes all of
it rows, or moves its cursor, it also notifies each listener that is registered
with it. The listener reacts by carrying out its implementation of the
notification method called on it.
RowSetobject creates an instance of
RowSetEventand passes it to the listener. The listener can use this
RowSetEventobject to find out which rowset had the event.
ResultSetMetaDatainterface, provides information about the columns in a
RowSetobject. An application can use
RowSetMetaDatamethods to find out how many columns the rowset contains and what kind of data each column can contain.
RowSetMetaData interface provides methods for
setting the information about columns, but an application would not
normally use these methods. When an application calls the
RowSet object will contain
a new set of rows, and its
RowSetMetaData object will have been
internally updated to contain information about the new columns.
RowSetobject that implements the
RowSetInternalinterface can call on the
RowSetReaderobject associated with it to populate itself with data. It can also call on the
RowSetWriterobject associated with it to write any changes to its rows back to the data source from which it originally got the rows. A rowset that remains connected to its data source does not need to use a reader and writer because it can simply operate on the data source directly.
RowSetobject gets access to its internal state and is able to call on its reader and writer. A rowset keeps track of the values in its current rows and of the values that immediately preceded the current ones, referred to as the original values. A rowset also keeps track of (1) the parameters that have been set for its command and (2) the connection that was passed to it, if any. A rowset uses the
RowSetInternalmethods behind the scenes to get access to this information. An application does not normally invoke these methods directly.
RowSetobject that has implemented the
RowSetInternalinterface can call on its reader (the
RowSetReaderobject associated with it) to populate it with data. When an application calls the
RowSet.executemethod, that method calls on the rowset's reader to do much of the work. Implementations can vary widely, but generally a reader makes a connection to the data source, reads data from the data source and populates the rowset with it, and closes the connection. A reader may also update the
RowSetMetaDataobject for its rowset. The rowset's internal state is also updated, either by the reader or directly by the method
RowSetobject that has implemented the
RowSetInternalinterface can call on its writer (the
RowSetWriterobject associated with it) to write changes back to the underlying data source. Implementations may vary widely, but generally, a writer will do the following:
RowSet interface may be implemented in any number of
ways, and anyone may write an implementation. Developers are encouraged
to use their imaginations in coming up with new ways to use rowsets.
IMPORTANT NOTE: Code that uses API marked "Since 1.6" must be run using a JDBC technology driver that implements the JDBC 4.0 API. You must check your driver documentation to be sure that it implements the particular features you want to use.
Submit a bug or feature
For further API reference and developer documentation, see Java SE Documentation. That documentation contains more detailed, developer-targeted descriptions, with conceptual overviews, definitions of terms, workarounds, and working code examples.
Copyright © 1993, 2014, Oracle and/or its affiliates. All rights reserved.