Personally I don't think there is anything wrong with having multiple mappings. You are doing the right thing by mapping to the same action and form. The jsp can define the action individually.
After reading Ted's book I think of mappings and actions as just presentation layer components that help with presentation layer flow, but shouldn't really care about accessing the business logic. It is difficult to explain, but I think it has taken me a 1.5 years of experience with Struts and re-reading the book to finally grasp the significance of what he is saying. Quite profound actually and I'm not just kissing ***. Hopefully I am not spilling the beans on everything in the book, but I highly recommend it for any architect. So in that sense- Have as many mappings as you like. Ideally these mappings should not be tied to any business logic. So for example if you call one mapping - you are calling it for the presentation component that you will present as well as the possible paths of success or failure. You should not be calling it because you know that it has some business logic that you want to execute. sandeep --- Michael Muller <[EMAIL PROTECTED]> wrote: > > It turns out that I can't pass the action into the > html:form tag using > tiles; that would involve nesting JSP tags. Grr. > > I guess my only recourse is to have the open > html:form tag in the > inserted body and the close html:form tag in the > template. Ick. > > So now I'm trying to figure out a way to have one > one action mapping. > Any ideas? Or alternative approaches? > > -- Mike > > Michael Muller wrote: > > > > My app has a bunch of wizard-style forms. I have > one "NextPageAction" > > Action class, and an separate mapping for each > page. The mappings all > > bind to the same form bean (a DynaValidatorForm) > and invoke the > > "NextPageAction". > > > > I was hoping to have only one action mapping, with > a whole bunch of > > forwards for "page1", "page2", etc. The problem > that prevents me from > > having one action mapping is validation: I need > the "input" attribute > > to redirect me to the correct wizard screen. > > > > So I went back to having lots of mappings. No big > deal. Until... > > > > I factored the "next" and "back" buttons into the > template. With those > > buttons, wend the closing "html:form" tag. Makes > sense to move the > > opening "html:form" tag into the template, too, > right? Oops, my action > > is in there. > > > > What do I do? > > > > I could leave the closing tag in the template and > the opening tag in the > > inserted body. Gross. > > > > I could try and pass the action into the template > through my tiles-defs. > > That's kinda kludgy, too. > > > > I'm back to thinking I should have one action > mapping. But I don't know > > how to accomplish this. > > > > Suggestions? > > > > Thanks, > > > > Mike > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > [EMAIL PROTECTED] > > For additional commands, e-mail: > [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
