I would just go a simpler route and have one form for all components. When you use ajax, only the model of the component that triggered the ajax call is updated and the others are left like they were. Besides being simpler and more efficient memory wise, it's also easier to convert back to non-ajax if you'd ever change your mind.
Eelco On 7/25/06, JK <[EMAIL PROTECTED]> wrote: > Hello, > > What is recommended way (Wicket 1.2.1, Ajax) to make table rows > editable? If table contains data: > > [edit] 1 abc > [edit] 2 def > [edit] 3 ghi > [edit] 4 jkl > > Should I have: > > [edit] 1 abc > hiddenForm1 > [edit] 2 def > formEditingItem2 > [edit] 3 ghi > hiddenForm3 > [edit] 4 jkl > hiddenForm4 > > Or is there way to add form when needed, like this: > > [edit] 1 abc > [edit] 2 def > formEditingItem2 > [edit] 3 ghi > [edit] 4 jkl > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Wicket-user mailing list > Wicket-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wicket-user > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
