On 4/20/06, Michael Jouravlev <[EMAIL PROTECTED]> wrote: > On 4/20/06, Rick Reumann <[EMAIL PROTECTED]> wrote: > > So again, really think about whether you need to go from one action to > > another. > > Lastly, if you do need to it (which from the above I doubt you need > > to), I wouldn't do it in the Action class but simply still return as > > usual but have your action-mapping forward to the new action. > > Won't work if you (1) want to redirect, (2) want to pass parameter > along, (3) do not want to use session.
1) Is true (but I'm not sure why he'd 'have' to do a redirect on the initial forward) 2) Is related to 1, but why does this matter when he can do request.setAttribute() which will work since he's doing a forward. Then in his resulting action he can pull it out with request.getAttribute() ? So he can't pass a request "parameter" but he certainly can forward and pass a "request attribute." If his logic is that complex that he needs to be handling a bunch of request parameters that don't even need to be handled in the initial action (and only need to be processed in the resulting nest action) then the design is SERIOUSLY messed up and he should reconsider what he's trying to do. 3) Again 3 only matters if you insist that a redirect become imperative on the initial 'action chain' which I'm not sure why it would 'have' to be. If it's critical that the URL look better than you can make sure that after you are in your forwarded action that you then do a proper redirect to a url that looks better. My 4) Most of this is probably moot since I don't think in this case he needs to action chain at all. -- Rick --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
