Author: ivaynberg
Date: Thu Dec 14 09:21:43 2006
New Revision: 487263
URL: http://svn.apache.org/viewvc?view=rev&rev=487263
Log:
javadoc fix: setOptimizeItemRemoval->setReuseItems
Modified:
incubator/wicket/branches/wicket-1.x/wicket/src/main/java/wicket/markup/html/list/ListView.java
Modified:
incubator/wicket/branches/wicket-1.x/wicket/src/main/java/wicket/markup/html/list/ListView.java
URL:
http://svn.apache.org/viewvc/incubator/wicket/branches/wicket-1.x/wicket/src/main/java/wicket/markup/html/list/ListView.java?view=diff&rev=487263&r1=487262&r2=487263
==============================================================================
---
incubator/wicket/branches/wicket-1.x/wicket/src/main/java/wicket/markup/html/list/ListView.java
(original)
+++
incubator/wicket/branches/wicket-1.x/wicket/src/main/java/wicket/markup/html/list/ListView.java
Thu Dec 14 09:21:43 2006
@@ -79,8 +79,8 @@
*
* <p>
* <strong>WARNING:</strong> though you can nest ListViews within Forms, you
- * HAVE to set the optimizeItemRemoval property to true in order to have
- * validation work properly. By default, optimizeItemRemoval is false, which
has
+ * HAVE to set the setReuseItems property to true in order to have
+ * validation work properly. By default, setReuseItems is false, which has
* the effect that ListView replaces all child components by new instances. The
* idea behind this is that you always render the fresh data, and as people
* usually use ListViews for displaying read-only lists (at least, that's what
@@ -89,7 +89,7 @@
* search for specific messages for these components fails as they are replaced
* with other instances. Another problem is that 'wrong' user input is kept as
* (temporary) instance data of the components. As these components are
replaced
- * by new ones, your user will never see the wrong data when
optimizeItemRemoval
+ * by new ones, your user will never see the wrong data when setReuseItems
* is false.
* </p>
*
