> From: "Ian Hunter" <[EMAIL PROTECTED]> > From the main page, I have the option for each user to "ask" for membership > in any group they don't currently belong in. They can hit one button that > forwards to a different action (groupinterest.do), with a forward called > "returnto" set to the main page. That action calls the exact same class as > updategroup.do, but that class knows to look for a forward called "returnto" > and either return to it or "pass it along" by storing it as a session > variable. When I do that, I store the entire ActionForward object, not just > the page name, so I catch requests to redirect as well as any other strange > config details of that forward.
So, if I follow this (and I'm not sure I do - either too much coffee or not enough :-) you've created an "indirection" step in your sequence that knows where to jump back to. I understand the part about tracking the entire ActionForward so that you pick up all the nuances of the forward params. Having re-read my posting, I realize I might not have been clear on one of the problem points - there are dozens of pages from which my user may choose to start this sequence. Doesn't your solution require a separate "indirection" step for each potential starting point - in order to code the approprite returnto forward? But you raise a very good point, that David's suggestion (simply caching the originating page name at sequence start time) doesn't address - capturing the nuances of the returnto page forward, such as redirect=true/false or perhaps even URL parameters. Jefficus --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
