It is practical to share the same action form by different actions, For example (I only listed two actions sharing the same form here, but the questions apply for multiple actions sharing the same form): <form-bean name ="sharedForm" type="myclassPath.SharedForm"/> <action path="/displayViewAction" type="myclasspath.DisplayViewAction" scope="session" name="sharedForm" validate="false"> </action> <action path="/saveDataAction" type="myclasspath.SaveDataAction" scope="request" name="sharedForm" validate="true" input="/View.jsp"> </action> Then the question is:is it a good practice to set up the sharedForm into different scope(session or request) for different actions, as what was shown in the above example? I believe this is a very good topic for Struts community and especially for those developed Struts framework. I appreciate your inputs very much! P.S. I have discussed this with a small group - company level, and the conclusion seems to be: No, this is not a good practice, since your putting the same shared action form will be confusing, and in practice saving the data into two duplicate form beans is not efficient and will cause errors.
--------------------------------- Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. Great rates starting at 1¢/min.