Two ways to attach such task.
�
First one is to use three different forms for these three actions, in the server side are there three action classes, UpdateAction, DeleteAction, AbortAction. Then define action path in struts' configuration file so that struts will invoke proper action class for different form submission.
I suspect that three different forms is out of the question in this case though.
Second one will utilize same action class and same form for all three operations. In the html page, different values are�used�for these three submit buttons. In the server side action class, you define three methods to handle different cases.� In this action class' perform function,�you check the submit button value and invoke proper method. This method is�similar to�front controller pattern.
But this is the exact reason LookupDispatchAction was created. HTTP sends the button label as the value of the submit button. I wholeheartedly disagree with hardcoding button labels in Java code! LDA was created to use the message resources as the source of the button label and indirect it through the button label key in the resources.
Erik
_______________________________________________ Juglist mailing list [EMAIL PROTECTED] http://trijug.org/mailman/listinfo/juglist_trijug.org
