Thank you so much for looking into this. It works like a charm now :).
By default, optimizeItemRemoval is set to false, which means that
ListView replaces all child components by new instances. The idea
behind this, is that you allways 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 behaviour.
I don't know, though if it is realistic to assume that ListViews are
usually only used to display read-only data. Think about two very common
use cases: a "shopping cart": you add n items to it, click on "view
cart" and
a list view displays the items with a TextField next to each of them
that shows the
quantity of the item and that you set to 0 if you want to remove the
item from your
cart.
And the use case in our application is that you can choose how many ppl
will book a trip
and that you have to be able to enter the names of each person. So I
have to display
a list with n rows and each row has TextFields that hold the sex, name
and birthdate of each person.
I think there are quite a few cases in which you need forms in listviews.
But then again: it works fine to have forms in listviews, just the
"hasErrorMessage" didn't return the value
I expected :)
- Johannes
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
