commons-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From simonetrip...@apache.org
Subject svn commit: r1186040 - /commons/proper/dbutils/trunk/src/site/xdoc/index.xml
Date Wed, 19 Oct 2011 09:00:54 GMT
Author: simonetripodi
Date: Wed Oct 19 09:00:54 2011
New Revision: 1186040

URL: http://svn.apache.org/viewvc?rev=1186040&view=rev
Log:
spaces in place of tabs

Modified:
    commons/proper/dbutils/trunk/src/site/xdoc/index.xml

Modified: commons/proper/dbutils/trunk/src/site/xdoc/index.xml
URL: http://svn.apache.org/viewvc/commons/proper/dbutils/trunk/src/site/xdoc/index.xml?rev=1186040&r1=1186039&r2=1186040&view=diff
==============================================================================
--- commons/proper/dbutils/trunk/src/site/xdoc/index.xml (original)
+++ commons/proper/dbutils/trunk/src/site/xdoc/index.xml Wed Oct 19 09:00:54 2011
@@ -37,23 +37,23 @@ update data.
 
 <p>Some of the advantages of using DbUtils are:</p>
 <ul>
-	<li>
-	    No possibility for resource leaks.  Correct JDBC coding isn't 
-	    difficult but it is time-consuming and tedious.  This often 
-	    leads to connection leaks that may be difficult to track down.
-	</li>
-	<li>
-    	Cleaner, clearer persistence code.  The amount of code needed 
-    	to persist data in a database is drastically reduced. The remaining 
-    	code clearly expresses your intention without being cluttered 
-    	with resource cleanup.
-	</li>
-	<li>
-	    Automatically populate JavaBean properties from ResultSets.  You
-	    don't need to manually copy column values into bean instances
-	    by calling setter methods.  Each row of the ResultSet can be
-	    represented by one fully populated bean instance.
-	</li>
+    <li>
+        No possibility for resource leaks.  Correct JDBC coding isn't 
+        difficult but it is time-consuming and tedious.  This often 
+        leads to connection leaks that may be difficult to track down.
+    </li>
+    <li>
+        Cleaner, clearer persistence code.  The amount of code needed 
+        to persist data in a database is drastically reduced. The remaining 
+        code clearly expresses your intention without being cluttered 
+        with resource cleanup.
+    </li>
+    <li>
+        Automatically populate JavaBean properties from ResultSets.  You
+        don't need to manually copy column values into bean instances
+        by calling setter methods.  Each row of the ResultSet can be
+        represented by one fully populated bean instance.
+    </li>
 </ul>
 
 </section>



Mime
View raw message