This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
If you want the link "automatically triggered" then why do you need it at all? Just go to the next page as a result of the action processing/result definition.
Joined: Jul 22, 2008
This is the "flow" that I need to have working:
1) Survey page, displaying one struts item that uses a dynamically generated list (based on the question number stored in a session variable, so I can display progress and such) in Survey.action
2) Clicking the submit button on the question page triggers Forward.action, which increments the question number and writes the previous answer to the database.
3) I need to refresh the Survey.action page, so that it can display the new question. Right now I have Forward.action dispatch to a second page, and then link back to the Survey.action page.
I want step 3 to happen automatically, but I need the survey page to be refreshed in order to get the new question displayed, and to keep this system flexible for multiple surveys.
I think I'm completely missing something about what you're saying, because the way I read that you're just submitting a form and redirecting to another page--like any other form processing, normal post-redirect.
As far as redirecting to an action, of course--you can either just put in the full action path to a normal "redirect" result type, or use "redirectAction" and put in only the action name.
You can also use OGNL expressions in the result configuration (whether XML- or annotation-based) if you need to pass something on in the redirect.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com