Yep +1.
I did the same. Implemented my own. I was nervous about using yet another
framework, when what I did instead was get a pen and paper and design it
from scratch. Yes I had some time to kill (Although not that much) but I
learnt a lot, about how users work as well as Struts.
Its not prefect, but when I need to change it, i know exactly what the code
does.
There you have my tupence worth.
----Original Message Follows----
From: <[EMAIL PROTECTED]>
Reply-To: "Struts Users Mailing List" <user@struts.apache.org>
To: <user@struts.apache.org>
Subject: RE: Implementing Wizards
Date: Thu, 27 Oct 2005 15:33:15 -0600
Hi Ross. I created a User Wizard to add Users to Microsoft Active Directory
from Linux. I did look at the Workflow Extensions as a possibility but I
found it cumbersome to use and chose to create a Wizard using pure Struts
and not the extensions. I have to tell you the Struts knowledge I gained
from doing it from scratch was worth the effort and it was great fun (I have
only been doing Struts for 2 1/2 weeks).
I used Struts 1.2.7 and used the LookupDispatchAction as the basis for my
Wizard. The book "Jakarta Struts Cookbook" on pages 199 to 203 gives a good
example of how to do this. Validating the Wizard form on pages 251 to 254
is good also.
The action mapping is as follows:
<!-- Wizard Mapping -->
<!-- Step 1 -->
<action path="/ViewStep1"
name="wizardForm"
scope="session"
type="org.apache.struts.actions.ForwardAction"
input="/step1.jsp"
parameter="/step1.jsp"
validate="false" />
<action path="/ProcessStep1"
name="wizardForm"
scope="session"
type="edu.nmsu.psl.userwizard.AddPSLUserWizardAction"
validate="true"
input="/step1.jsp"
parameter="methodToCall">
<forward name="next" path="/ViewStep2.do" />
<forward name="badnext" path="/ViewStep1.do" />
</action>
<!-- Step 2 -->
<action path="/ViewStep2"
name="wizardForm"
scope="session"
type="org.apache.struts.actions.ForwardAction"
validate="false"
input="/step2.jsp"
parameter="/step2.jsp" />
<action path="/ProcessStep2"
name="wizardForm"
scope="session"
input="/step2.jsp"
type="edu.nmsu.psl.userwizard.AddPSLUserWizardAction"
validate="true"
parameter="methodToCall">
<forward name="previous" path="/ViewStep1.do" />
<forward name="next" path="/ViewStep3.do" />
</action>
<!-- Step 3 -->
<action path="/ViewStep3"
name="wizardForm"
scope="session"
input="/step3.jsp"
validate="false"
type="org.apache.struts.actions.ForwardAction"
parameter="/step3.jsp" />
<action path="/ProcessStep3"
name="wizardForm"
scope="session"
input="/step3.jsp"
validate="true"
type="edu.nmsu.psl.userwizard.AddPSLUserWizardAction"
parameter="methodToCall">
<forward name="previous" path="/ViewStep2.do" />
<forward name="finish" path="/wizard_done.jsp" />
</action>
</action-mappings>
-----Original Message-----
From: Ross Gibb [mailto:[EMAIL PROTECTED]
Sent: Thu 10/27/2005 2:58 PM
To: Struts Users Mailing List
Subject: Implementing Wizards
I know this comes up from time to time and yes I have read the previous
posts on implementing wizard like interfaces. As a result of previous
posts I decided to give Struts Workflow Extension a shot,
http://www.livinglogic.de/Struts/. I implemented a simple five screen
wizard like interface for adding a new user to my system. I did get it
to work the way I wanted. However, I found that using Struts Workflow
Extension was often counter-intuitive and at times frustrating. Also, I
am using Struts 1.2.7 and I will have to make a few bug fixes to the
Struts Workflow Extension code to make it work properly.
My question is: has anyone used Struts Workflow Extension and then
switched to another wizard tool kit and found it to be superior to
Struts Workflow Extension? I am specifically looking for input from
people who have actually used Struts Workflow Extension because even
though I knock it, I did get it to work the way I wanted it to and I am
reasonably sure I can easily fix the bugs I am experiencing with it.
Thanks,
Ross
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
