Java Doc for ListView.java in  » J2EE » wicket » wicket » markup » html » list » Java Source Code / Java DocumentationJava Source Code and Java Documentation

Example:

 <tbody>
 <tr wicket:id="rows" class="even">
 <td><span wicket:id="id">Test ID</span></td>
 ...    
 

Though this example is about a HTML table, ListView is not at all limited to HTML tables. Any kind of list can be rendered using ListView.

The related Java code:

 add(new ListView("rows", listData)
 {
 public void populateItem(final ListItem item)
 {
 final UserDetails user = (UserDetails)item.getModelObject();
 item.add(new Label("id", user.getId()));
 }
 });
 

WARNING: 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 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 we think), this is good default behavior.
However, as the components are replaced before the rendering starts, the 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 is false.

be carefull to add any components to the list item.

be carefull to add any components to the list item. So, don't do:

 add(new Label("foo", "bar"));
 

 item.add(new Label("foo", "bar"));