Friday, March 13, 2009

What is the difference between cached rowset, jdbrowset and

Question :What is the difference between cached rowset, jdbrowset and
webrowset? (JDBC)

Answer :A CachedRowSet is a disconnected, serializable, scrollable container for
tabular data. A primary purpose of the CachedRowSet class is to provide a
representation of a JDBC ResultSet that can be passed between different
components of a distributed application. For example, a CachedResultSet
can be used to send the result of a query executed by an Enterprise
JavaBeans component running in a server environment over a network to a
client running in a web browser. A second use for CachedRowSets is to
provide scrolling and updating for ResultSets that don't provide these
capabilities themselves. A CachedRowSet can be used to augment the
capabilities of a JDBC driver that doesn't have full support for scrolling and
updating. Finally, a CachedRowSet can be used to provide Java
applications with access to tabular data in an environment such as a thin
client or PDA, where it would be inappropriate to use a JDBC driver due to
resource limitations or security considerations. The CachedRowSet class
provides a means to "get rows in" and "get changed rows out" without the
need to implement the full JDBC API.
A JdbcRowSet is a connected rowset that wraps a ResultSet object. The
main use of JdbcRowSet is to wrap a ResultSet and make it appear as a
JavaBeans(tm) component.
The WebRowSet class extends CachedRowSet with the ability to write out
the state of the the RowSet as an XML document. The format of the XML
document is described by the DTD 'RowSet.dtd'.

No comments: