i meant that forwardYYY() method for every globalForward can be in some BaseAction class and all XXXActionBase classes could extend this BaseAction class. That could help to manage all global forward in one class.
Yes, this is one possible option.
But since all the XXXActionBase classes are generated, whether the code is in one place or is duplicated is not a big issue.
the other issue is when i draw forward on story board from action to action or page that is global forward i can't say "use global forward" i must create new dynamic forward to target of global forward. in generated class then i got two forwards (global & dynamic) which point to same target.
i hope you understand what i mean.
This is a 'feature' inherited from Struts. In Struts, when an Action forwards to a globalForward, it is done in code and the struts-config.xml gives no information about this.
In other words, if you need to use globalForward, the 'proper' way to do it is you don't draw a forward from action 1 to action 2 on the Storyboard. Instead, you just do the forward in code.
As you can see, doing this means you don't see the flow on the Storyboard. Therefore, IMO, GlobalForwards should be used only for forwarding to exception handling pages and the welcome pages.
Maybe you call tell me what you have in mind. How will you see it works?
John Yu Scioworks Technologies
e: [EMAIL PROTECTED] w: +(65) 873 5989
w: http://www.scioworks.com m: +(65) 9782 9610
Scioworks Camino - "Rapid WebApp Assembly for Struts"
