Click to remove the first line: you will notice that the second line is removed! That is the first strange thing. Same problem when removing the second item.
It only looks like that. The childs should have been removed. If you update, you'll find the changes.
Now another test: replace the first line with value «Hello» and click to remove the third line. You will notice that the text you have entered is reset.
Yep, that is true. Normal links are used, and thus any other fields are not included in the submit.
We need to allow to use SubmitLink instead of Link.
That might work.
But this won't be sufficient: ListView currently removes rows and re-populates them from the model. This clearly means user input is lost.
I don't think so. If we use a submit link, first the models would be updated, and then the link with the delete behavior would be executed. On a side note, Johan I don't remember exactly anymore why this has to be done on object identity. This obviously doesn't work properly if you have multiple references of the same object (or object with the same identity) in the list. Why wouldn't just using the index work work again?
Because of the necessary incompatible changes, I think ListView should be forked
We're working on 1.3 and 2.0, for which a few breaks are permitted.
, unless there is another Wicket component that fits the job?
Wicket-exention's repeater package was set up to be a better ListView. You might try that. Eelco
