One elegant and secure solution is to use session-scope forms, with a clever reset, and transactional support; just be sure you have the appropriate hardware resources.
If you don't like session-scoped beans, then you're back to writing hidden fields. Of course, this doesn't have to be difficult, since a single <bean:write> method could generate any number of hidden fields easily enough. The third solution would be to use another store beside the session (like a database), but that has its own performance consequences. Web development: Welcome to the jungle =:0) -Ted. 11/11/2002 9:46:40 PM, James Higginbotham <[EMAIL PROTECTED]> wrote: >Anyone written or seen an elegant solution to this? > >James -- To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org>
