Maybe I missed a bit, but do you not always have page flow coded in JSP AND Action
classes?
This should be the exception ! Not the rule.
In the action the server decides what to do with user input and what page to go next.
No. The action just says success, error or whatever return
None of the 4 ways described in the user guide suits me...
1- Using html:link module=moduleB path=/menu.do/ means page flow
is coded in JSP
2- Using ActionMapping means you are coding a Action class
3- Using global-forwards means you are coding a Action class or
referencing it in a html:link =
: Re: Q: Switching Modules
None of the 4 ways described in the user guide suits me...
1- Using html:link module=moduleB path=/menu.do/ means
page flow is coded in JSP
2- Using ActionMapping means you are coding a Action class
3- Using global-forwards means you are coding a Action class
jean kon-sun-tack wrote:
In my companyList screen I have a cancel button (/companyList/cancel.do).
In moduleA-struts.xml, why can't I have something like :
action path=/companyList/cancel forward=/menu.do
module=moduleB redirect=true/
I want my page flow configured in my xml config files,
In my companyList screen I have a cancel button (/companyList/cancel.do).
In moduleA-struts.xml, why can't I have something like :
action path=/companyList/cancel forward=/menu.do
module=moduleB redirect=true/
I want my page flow configured in my xml config files, not in my JSPs by doing :
5 matches
Mail list logo
