If the "tmscode" is a property on the ActionForm, and Action A and Action B both use an ActionForm with a "tmscode" property, then the property will be available to Action B too.
Changing "tmscode" in Action A and then having the change available to Action B can be problematic, since each Action autopopulates its form from the request. The usual advice is to examine your motivations for forwarding from one Action to another. Often people start to do this because businwss logic is embedded in an Action that would be better placed behind a business facade. Ideally, the business logic in an Action should be one or two method calls to a business facade. What is Action B doing that Action A cannot? Why can't both Actions make the same calls to the business facade? HTH, Ted. On 4/19/06, Meenakshi Singh <[EMAIL PROTECTED]> wrote: > Thanks a lot for your response. > > I have a tmscode in the request of action A. Now I would want this code to > be available in the request of action B. Would you please tell me how would > this tmscode be available to action B so that it can render the desired jsp > as per that tmscode. > > Thanks & Regards, > MS. > > -----Original Message----- > From: Gary Feidt [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 18, 2006 7:27 PM > To: user@struts.apache.org > Subject: Re: Calling another action from an action > > > You can simply use return mapping.findForward("actionB"); > > and the following in the struts-config.xml: > > <forward name="actionB" path="ActionB.do"/> > > Gary > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- HTH, Ted. ** http://www.husted.com/ted/blog/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
