Re: Designs for Wizard workflow...

2005-08-04 Thread Michael Jouravlev
Two years ago you would be on your own. Now you have a bunch of solutions:

* Struts Workflow Extension: 
  http://www.livinglogic.de/Struts/index.html
* Struts Flow: 
  http://struts.apache.org/flow/index.html
* Spring Web Flow: 
  http://struts.apache.org/flow/index.html
* And my very own, WizardAction implementing Easy Wizard:
  http://struts.sourceforge.net/strutsdialogs/wizardaction.html

Of course, I would prefer you to use my solution ;-) and I am here to
help if you need. See the live demo here:
http://www.superinterface.com/strutsdialog/wizardaction.do
and a slightly different version here:
http://www.superinterface.com/wizard/signupWizard.do

I use DispatchAction flavor, like your second choice.

But I've listed other flow engines for you too.

Michael.

On 8/4/05, Swapnil Patil <[EMAIL PROTECTED]> wrote:
> Hi all,
> 
> I am converting Wizard workflow into Struts framework.
> Wizard page contains next,back,finish buttons.
> I am considering 2 approches..
> 
> 1)
> /PrepareStep1.do -- step1Form --> forward to step1.jsp
> step2.jsp
> on next ---> ProcessStep1.do
> 
> 
> /ProcessStep1.do --step1Form -->on success /PrepareStep2.do
> 
> /PrepareStep2.do --step2Form --> on success forword to step2.jsp
> 
> step2.jsp
> on next ---> ProcessStep2.do
> on back ---> PrepareStep3.do
> 
> /ProcessStep2.do --step2Form --> /PrepareStep3.do
> 
> 
> PrepareStep1 will fill the form step1Form to render the jsp page step1.jsp .
> step1.jsp on submit forwrd to /ProcessStep1.do . /ProcessStep1.do on success
> forward to /PrepareStep3.do . and so one...
> 
> Each ProcessAction will save the data from Form to Business object.
> 
> 
> 
> 2) One common ActionForm (session scope) will be used be all actions.
> 
> /PrepareStep1.do -- commonForm --> forward to step1.jsp -->
> /ProcessStep1AndPrepareStep2.do ---> step2.jsp >
> /ProcessStep2AndPrepareStep3.do
> 
> I read somewhere that DispatchAction with common Form is suitable for Wizard
> workFlow applications. My wizarsd must support next,back.
> 
> 
> 
> 
> Which approch is better? on the following points
> 1> Extesion of wozard steps.(may be in between the old steps)
> 2> Maintenance
> 
> Can any body tell me the advantage and disadvantage of both of these
> approach.
> 
> Waiting for suggetion
> 
> Thanks & Regard
> Swapnil

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Designs for Wizard workflow...

2005-08-04 Thread Swapnil Patil
Hi all,

I am converting Wizard workflow into Struts framework.
Wizard page contains next,back,finish buttons.
I am considering 2 approches..

1) 
/PrepareStep1.do -- step1Form --> forward to step1.jsp
step2.jsp
on next ---> ProcessStep1.do


/ProcessStep1.do --step1Form -->on success /PrepareStep2.do 

/PrepareStep2.do --step2Form --> on success forword to step2.jsp

step2.jsp
on next ---> ProcessStep2.do
on back ---> PrepareStep3.do

/ProcessStep2.do --step2Form --> /PrepareStep3.do


PrepareStep1 will fill the form step1Form to render the jsp page step1.jsp . 
step1.jsp on submit forwrd to /ProcessStep1.do . /ProcessStep1.do on success 
forward to /PrepareStep3.do . and so one... 

Each ProcessAction will save the data from Form to Business object.



2) One common ActionForm (session scope) will be used be all actions.

/PrepareStep1.do -- commonForm --> forward to step1.jsp --> 
/ProcessStep1AndPrepareStep2.do ---> step2.jsp > 
/ProcessStep2AndPrepareStep3.do 

I read somewhere that DispatchAction with common Form is suitable for Wizard 
workFlow applications. My wizarsd must support next,back.




Which approch is better? on the following points
1> Extesion of wozard steps.(may be in between the old steps)
2> Maintenance 

Can any body tell me the advantage and disadvantage of both of these 
approach. 

Waiting for suggetion 

Thanks & Regard
Swapnil