Interesting... I wonder if the answer would be different if you make the distinction between forwarding to another Action and just calling execute() of another Action. I think both have problems certainly, but just calling execute() seems a little less offensive to me because there is a greater degree of control over what is being done (i.e., no auto-population to worry about for instance).
Just calling execute() is pretty innocuous, but at that point, the question becomes "what's the correct way to get a handle on that action instance." In fact, one of Ted's ideas for a ViewController was simply to use the Action interface rather than making something new. I don't love that, because I think the semantics of what the ActionMapping and ActionForm would be aren't too clear.
The real objection is to invoking RequestProcessor.process(), which is ultimately what happens if you call RequestDispatcher.forward() or RequestDispatcher.include() (which, in turn, is ultimately what happens if you return an ActionForward which maps to a Struts Action or use a Struts action as the input forward for a form).
Joe
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "In fact, when I die, if I don't hear 'A Love Supreme,' I'll turn back; I'll know I'm in the wrong place."
- Carlos Santana
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
