You can do this by declaring the method that will handle the request. My suggestion on this is that you should see if you REALLY need only one action to handle everything. This might make maintenance more difficult and you might have to mingle member variable that deal with different requests and make the code more obscure. Usually I keep the same action class for things that are related. (e.g. User login / logout, Password change/reset).
Anyhow: Here is how you can go about configuring stratus.xml to call a prticular method. <action name="blah" class="MySingleAction" method="blah"> ... </action> <action name="foo" class="MySingleAction" method="foo"> ... </action> Regards, hf On 4/20/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hi, I have 5-6 Jsp pages and all are inter connected. If any one make changes, these changes should be display in the database. In this case, I need only one Action class which can hold or manipulate all changes from all jsp pages. I am not sure "Can we keep one action file for all jsp files?" If yes, then how can we configure struts-config.xml file. If no, then pls suggest me any altenative solution. Thanks & Regards, Prafull Jain The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com
