Most often, they would at least have their own ActionMapping. Whether they share the same Action or not varies quite a bit, and often depends on the needs of your business logic. Generally, the simplest thing is to use the DispatchAction.
As a rule, it's best to minimize the number of Action classes, since they are instantiated once and stay instantiated for the life of the application. -- Ted Husted, Husted dot Com, Fairport NY US -- Developing Java Web Applications with Struts -- Tel: +1 585 737-3463 -- Web: http://husted.com/about/services Tom Brunner wrote: > > Hi all, > > Sorry, but I am somewhat new to Struts and have a > question related to similar actions. I have a group of > ActionForms. All of these forms are related to an > 'enter', 'process', and 'edit' action. > > What is the best way to go about organizing the Action > classes associated with these? Should they all have > their own action or should they use DispacthAction or > should they all be one action checking for some sort > of request paramter? > > Thanks in advance for your input and help... > > -Tom > > __________________________________________________ > Do You Yahoo!? > Yahoo! Sports - Coverage of the 2002 Olympic Games > http://sports.yahoo.com > > -- > 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]>
