Correct me if I am wrong, but if you are doing a multipage form you
have to put the form into the session scope in order to retain it
throughout the duration of the wizard, am I right? The only way to
avoid it would be to place hidden fields in the second and third
pages to hold the values so they continue to get passed along which
would be ridiculous.
The reason I bring this up because the following snippet shows up in
the validator example that ships with struts:
<!-- Multi-Part Registration Action -->
<action path="/multiRegistration"
type="org.apache.struts.webapp.validator.MultiRegistrationAction"
name="multiRegistrationForm"
scope="request"
validate="false">
<forward name="success" path="/index.jsp"/>
<forward name="input1" path="/multiRegistration1.jsp"/>
<forward name="input2" path="/multiRegistration2.jsp"/>
</action>
If the scope is request, how is it possible to retain the form
values until the last step? If this is indeed an issue, perhaps it
should be updated before struts 1.1 (I would also comment on the
validate="false" but I know that is a bug in the DynaValidatorForm
with multipages, so I will leave that argument until post-1.1).
Dan
--
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Daniel Allen, <[EMAIL PROTECTED]>
http://www.mojavelinux.com/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
There is no such thing as a casual knowledge of xslt, either
you know everything about it or you are sitting in the creek.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
