Good find! We should fix that. Could you file a bug?
Eelco
Cameron Braid wrote:
I have a page with a form that contains a pagenated list, with a grid like input form (i.e. a textfield per list item)
The list model contains 6 elements.
The page size is 5.
It displays the first 5 elements fine, with values in each text box.
If I then navigate to the second page, it shows the last element’s input box.
I then submit the form.
I then navigate back to the first page and all of the text boxes are empty.
It appears that the submit process traverses all components in the form (which means all list items in the list) and gets them to update their model. This is setting null into my list item properties.
Is wicket able to cater for this, and only update the form elements that were actually on the screen, or do I need to do something special ?
Thanks.
Cameron
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
