You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by rd...@apache.org on 2003/09/17 22:23:22 UTC
cvs commit: jakarta-commons/beanutils/src/java/org/apache/commons/beanutils package.html
rdonkin 2003/09/17 13:23:22
Modified: beanutils/src/java/org/apache/commons/beanutils package.html
Log:
Applied documentation patch submitted by Matthew Sgarlata.
Revision Changes Path
1.17 +8 -9 jakarta-commons/beanutils/src/java/org/apache/commons/beanutils/package.html
Index: package.html
===================================================================
RCS file: /home/cvs/jakarta-commons/beanutils/src/java/org/apache/commons/beanutils/package.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- package.html 28 Aug 2003 21:10:36 -0000 1.16
+++ package.html 17 Sep 2003 20:23:22 -0000 1.17
@@ -71,7 +71,7 @@
learn about the properties and operations provided by your class, and present
them in a visually appealing manner in development tools.</p>
-<p>The <a href="http://java.sun.com/javabeans/docs/spec.html">JavaBeans
+<p>The <a href="http://java.sun.com/products/javabeans/docs/spec.html">JavaBeans
Specification</a> describes the complete set of characteristics that makes
an arbitrary Java class a JavaBean or not -- and you should consider reading
this document to be an important part of developing your Java programming
@@ -515,12 +515,11 @@
<a name="dynamic.rowSet"></a>
<h3><code>RowSetDynaClass</code> (Disconnected ResultSet as DynaBeans)</h3>
-
-<p>Although <a href="#dynamic.resultSet">ResultSetDynaClass</code> is a very
-useful technique for representing the results of an SQL query as a series of
-DynaBeans, an important problem is that the underlying <code>ResultSet</code>
-must remain open throughout the period of time that the rows are being
-processed by your application. This hinders the ability to use
+<p>Although <a href="#dynamic.resultSet"><code>ResultSetDynaClass</code></a> is
+a very useful technique for representing the results of an SQL query as a
+series of DynaBeans, an important problem is that the underlying
+<code>ResultSet</code> must remain open throughout the period of time that the
+rows are being processed by your application. This hinders the ability to use
<code>ResultSetDynaClass</code> as a means of communicating information from
the model layer to the view layer in a model-view-controller architecture
such as that provided by the <a href="http://jakarta.apache.org/struts/">Struts
@@ -544,7 +543,7 @@
DynaBeans that correspond to each row of the result) can be conveniently
serialized and deserialized (as long as the underlying column values are
also Serializable). Thus, <code>RowSetDynaClass</code> represents a very
-convenient way to transmit the results 0f an SQL query to a remote Java-based
+convenient way to transmit the results of an SQL query to a remote Java-based
client application (such as an applet).</p>
<p>The normal usage pattern for a <code>RowSetDynaClass</code> will look
@@ -760,7 +759,7 @@
// filter the Collection
CollectionUtils.filter( peopleCollection, predicate );
-</pre</code>
+</pre></code>
</p>
<a href="bean-property-transformer"></a>