On Wed, 2004-08-25 at 15:03, Rick Reumann wrote: > Sebastian Ho wrote: > > > I am already using DispatchAction. > > > > I didn't use the scope in my action-mapping. Instead I use > > session.setAttribute in my Action. > > More than likely you don't need to do the above (you can give your form > Session scope right on the mapping for the Action in your config). > > > The codes to update the actionform is in action1. But I need to update > > the same form in action2. > > If you are using a DispatchAction why would you be updating the form in > a totally different Action? You normally keep related action tasks > together in one DispatchAction.
Maybe I need to refactor my codes. I grouped them into two action classes but in that particular JSP, methods from both action classes are used.. > > > One way is to duplicate the same codes in both > > action. Or the common update codes can be executed before a JSP is > > loaded. The latter will prevent duplicate codes. > > Sorry, it might be a language barrier, but you have me really lost now:) > I'm not sure what you are trying to in the above. Not to worry. Maybe my situation is kinda complex to explain clearly. I should be able to resolve the problem after I refactor the codes. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
