Although I have not yet tried it, you might consider
subclassing your WizardAction. WizardAction would
have all of the methods necessary to perform the
entire task, then have one subclass for each of the
steps all the while using the same WizardForm.
WizardAction extends Action
WizardStep1Action extends WizardAction.
WizardStep2Action extends WizardAction.
This would allow you to map the seperate steps into
the struts-config file where they are identifiable and
the forwards are configurable, but still maintain the
majaority of the business logic in one class.
Bob Byron
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
