Print this page


@@ -74,11 +74,11 @@
 object, that is, it 
 <b>must</b> continually maintain its connection to its data source using a JDBC
 technology-enabled driver ("JDBC driver"). In addition, a <code>JdbcRowSet</code>
 object provides a fully updatable and scrollable tabular 
 data structure as defined in the JDBC 3.0 specification.
 <li><a href="CachedRowSet.html">
  - A <tt>CachedRowSet</tt> object is a JavaBeans&trade;
  component that is scrollable, updatable, serializable, and generally disconnected from
  the source of its data. A <tt>CachedRowSet</tt> object

@@ -90,11 +90,11 @@
 Typically a <code>SyncProvider</code> implementation relies upon a JDBC
 driver to obtain connectivity to a particular data source.
 Further details on this mechanism are discussed in the <a
 href="spi/package-summary.html"><code>javax.sql.rowset.spi</code></a> package
 <li><a href="WebRowSet.html"><b><code>WebRowSet</code></b></a> - A 
 <code>WebRowSet</code> object is an extension of <tt>CachedRowSet</tt>
 that can read and write a <code>RowSet</code> object in a well formed XML format.
 This class calls an <a href="spi/XmlReader.html"><code>XmlReader</code></a> object 
 (an extension of the <a href="../RowSetReader.html"><code>RowSetReader</code></a>

@@ -106,11 +106,11 @@
 <code>SyncFactory</code> in the form of <code>SyncProvider</code>
 implementations. In order to ensure well formed XML usage, a standard generic XML
 Schema is defined and published at
 <a href="">
 <li><a href="FilteredRowSet.html"><b><code>FilteredRowSet</code></b></a> - A
 <tt>FilteredRowSet</tt> object provides filtering functionality in a programmatic
 and extensible way. There are many instances when a <tt>RowSet</tt> <code>object</code>
 has a need to provide filtering in its contents without sacrificing the disconnected
 environment, thus saving the expense of having to create a connection to the data source.

@@ -122,11 +122,11 @@
 <code>FilteredRowSet</code> object is tasked with enforcing the set filter for both
 inbound and outbound read and write operations. That is, all filters can be
 considered as bi-directional. No standard filters are defined;
 however, sufficient mechanics are specified to permit any required filter to be
 <li><a href="JoinRowSet.html"><b><code>JoinRowSet</code></b></a> - The <tt>JoinRowSet</tt>
 interface  describes a mechanism by which relationships can be established between 
 two or more standard <code>RowSet</code> implementations. Any number of <tt>RowSet</tt>
  objects can be added to a <tt>JoinRowSet</tt> object provided  the <tt>RowSet</tt>objects 
 can be related  in a SQL <tt>JOIN</tt> like fashion. By definition, the SQL <tt>JOIN</tt> 

@@ -144,11 +144,11 @@
 specification. The following paragraphs outline a number of starting points for
 implementers of the standard JDBC <code>RowSet</code> definitions. Implementers
 should also consult the <i>Implementer's Guide</i> in the <a
 href="spi/package-summary.html">javax.sql.rowset.spi</a> package for guidelines
 on <a href="spi/SyncProvider.html"><code>SyncProvider</code></a> implementations.
 <li><b>3.1 Constructor</b>
     All <code>RowSet</code> implementations <strong>must</strong> provide a
 no-argument constructor.

@@ -213,15 +213,14 @@
               <td valign="top">Provides fields for storing of stream instances
   in addition to providing a set of constants for stream type designation.<br>
 <li><b>3.3 Connected RowSet Requirements</b>
 The <code>JdbcRowSet</code> describes a <code>RowSet</code> object that <b>must</b> always
 be connected to the originating data source. Implementations of the <code>JdbcRowSet</code>
 should ensure that this connection is provided solely by a JDBC driver. 

@@ -229,11 +228,10 @@
 <code>JdbcRowSet</code> interface and are therefore operating in a connected environment
 do not use the <code>SyncFactory</code> to obtain a <code>RowSetReader</code> object
 or a <code>RowSetWriter</code> object. They can safely rely on the JDBC driver to
 supply their needs by virtue of the presence of an underlying updatable and scrollable
 <code>ResultSet</code> implementation.
 <b>3.4 Disconnected RowSet Requirements</b>
 A disconnected <code>RowSet</code> object, such as a <code>CachedRowSet</code> object, 

@@ -246,19 +244,19 @@
 <code>SyncProvider</code> object ensures that the critical JDBC properties are 
 maintained in order to re-establish a connection to the data source when a 
 synchronization is required. A disconnected <code>RowSet</code> object should 
 therefore ensure that no 
 extraneous references remain on the <code>Connection</code> object.
 <li><b>3.5 Role of RowSetMetaDataImpl</b>
 The <code>RowsetMetaDataImpl</code> class is a utility class that provides an implementation of the
 <a href="../RowSetMetaData.html">RowSetMetaData</a> interface, supplying standard setter
 method implementations for metadata for both connected and disconnected 
 <code>RowSet</code> objects. All implementations are free to use this standard
 implementation but are not required to do so.
 <li><b>3.6 RowSetWarning Class</b>
 The <code>RowSetWarning</code> class provides warnings that can be set
 on <code>RowSet</code> implementations.
 Similar to <a href="../../../java/sql/SQLWarning.html">SQLWarning</a> objects,

@@ -271,12 +269,10 @@
 <code>getRowSetWarnings</code> methods, the <code>RowSetWarning</code> method
 <code>getNextWarning</code> can be called on it to retrieve any warnings that might
 be chained on it.  If a warning is returned, <code>getNextWarning</code> can be called
 on it, and so on until there are no more warnings.
 <li><b>3.7 The Joinable Interface</b>
 The <code>Joinable</code> interface provides both connected and disconnected 
 <code>RowSet</code> objects with the capability to be added to a 
 <code>JoinRowSet</code> object in an SQL <code>JOIN</code> operation.