Ken, More than likely you sould just have the one button for the entire list.
As for only updating the rows that have changed, you'll have to track and manage that yourself. When the incomming data arrives, you'll have to match it against what you served, and find out the updated rows that way. If you have to avoid session storage, then it will become next to impossible without some client side logic. Not a 100% nice, but that's the way it is for everyone. I think the easiest way is if the rows are substantial enough, to send out for updates on an individual basis... ie: edit links on a row, click, go to a page to update that row, etc etc etc. It's a problem that would be nice to solve... need to give it more thought, unless anyone else has the elegant solution already made?... Arron. Struts Newsgroup (@Basebeans.com) wrote: >Subject: nested:iterate and updating a database >From: "Ken Holzer" <[EMAIL PROTECTED]> > === >Hi All, > >I have a form that is using the nested:iterate tag to display several rows >from a database table. My question is do I need a submit (update) button on >each row or can I have one update button? > >If I can have one, button how do I update the database based on the data >that was changed on the form? > >Any sample code for the Action Form would be appreciated. > >Thanks, > >Ken Holzer > > > >-- >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
