I'm actually implementing this in Struts at the moment (haven't quite finished pushing WebWork through the standards process), but using a tip from Gavin, I've made Struts behave more like WebWork by moving the action logic into the form. Now I only need to create new forms and I can reuse the same action over and over (any ideas for names for these support classes?).
I think I'd break things down differently with the form and logic together than I would if the form and logic were separate (as in plain Struts). Do you guys have any tips on how you'd implement this in WW?
Much appreciated, Bob
Begin forwarded message:
From: Bob Lee <[EMAIL PROTECTED]> Date: Tue Oct 7, 2003 6:31:19 AM US/Central To: [EMAIL PROTECTED] Subject: Wizard with a Twist Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
All,
I have requirements do develop a wizard like application where you can have multiple questions (up to 3) on a single page.
When there are multiple questions, the first appears, you select an answer, and the next one appears. If you change the answer to a previous question, all of the succeeding answers are reset and you have re-answer the questions.
What the next question is bears on the answers to the previous questions (or some other factors). I've deemed it okay to go back to the server each time.
There's also a requirement to do a bread crumb trail, but it will need to go back pages of questions (not one question at a time). Also, going forward, if questions have been answered and you don't alter the answers, you should be able to go forward page by page as well.
I'm trying to figure out the best way to break this down (i.e. how many JSPs, actions, and forms to use, what scope to use for the forms, etc.). Key factors for maintainability will be the naming schemes (so you can easily follow and manipulate the flow) and the ability to move questions around without impacting other questions too much or making changes in too many places. Any tips or suggestions?
Note: I started down a more generic route where I was going to build a tool to manage the flow, but there's so many weird requirements (things specific to certain questions, etc.) that I decided it would be easier to just start out simple for this iteration.
Thanks, Bob
P.S. I also have an option to use Blue Martini. Anyone have experience with this? Would it help me solve this problem more easily than just coding it with Struts?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
