Hi, I read your article and found it very informative. But in my situation, I have about 10 different "items". If I use the technology described in the paper, I need to create about 40 forms and even more actions. Is there any other ways to get around of this?
Thanks, --- Michael Jouravlev <[EMAIL PROTECTED]> wrote: > On 6/6/05, Tony Smith <[EMAIL PROTECTED]> wrote: > > Hi, I am using struts to develop a webapp. One > piece > > of work is the user information. I will allow user > to > > create, view, and update his personal information. > > Maybe you would like to reconsider your three pages, > and split them > into "edit new", "vew existing" and "edit existing" > plus a separate > action just to create a new userinfo? In that case > you might find this > worth reading: > http://www.theserverside.com/articles/article.tss?l=RedirectAfterPost2 > > > Usually, the three pages are very similar. What is > the > > best way to do this with Struts? Is there any > > "Pattern" for this? I checked the Struts > > DispatchAction, but > > not sure how to do it... > > DispatchAction simply allows you to define handler > methods for events, > usually triggered by submit buttons. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > __________________________________ Discover Yahoo! Use Yahoo! to plan a weekend, have fun online and more. Check it out! http://discover.yahoo.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
