It doesn't matter as long as you can justify it :-) If the behaviors "belong" together, you may choose to use a Dispatch-like action. Otherwise, make them separate. Alot of this is stylistic but you'll figure out the answer based on how related the business code is.
Paul On 9/12/07, Zhang, Larry (L.) <[EMAIL PROTECTED]> wrote: > > > Say I have two version design: > > (1) > <html:form styleId="myForm" action="/myAction.do"> > Some other things go here... > <a class="myStyleclass1" id="myAnalyst" > href="/MyWeb/showSomeInfo.do">onePeople</a> > <a class="myStyleclass1" id="myEmployee" > href="/MyWeb/showEmployeeInfo.do">one Employee</a> > <html:submit property="submitButtonName" styleClass="MyStyleClass2" > styleId="Save" value="Save"/> > </html:form> > > (2) > <html:form styleId="myForm" action="/myAction.do"> > Some other things go here... > <a class="myStyleclass1" id="myAnalyst" > href="/MyWeb/myAction.do?pageId=1">one People</a> > <a class="myStyleclass1" id="myEmployee" > href="/MyWeb/myAction.do?pageId=2">on Employee</a> > <html:submit property="submitButtonName" styleClass="MyStyleClass2" > styleId="Save" value="Save"/> > </html:form> > > The verion 1 has three actions to render three pages, while version 2 > use one action to render three pages. The arguments for version 1 is > that three instances of the action class (one is myAction - which is > relatively big, others are smaller) is betther than three instnaces of a > bigger action classes (myAction). Does this make sense? Does the number > of action intances matters? > > Thanks. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
