> -----Original Message-----
> From: Ted Husted [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, October 12, 2005 5:44 PM
> To: Struts Developers List
> Subject: Re: Reset for DynaActionForm
>
> Right now, a lot of Java web applications flit from action to action.
> We migth use one action to display the page the first time,
> and then submit to another action after the form is filled
> out, and so forth.
In Struts, this is because if an action mapping requires a form, the
values have to be there when that mapping is called. Again, from my
example:
<action path="/edit" type="PrepareFormAction"/>
<action path="/save" type="SubmitFormAction" name="myForm" input="/edit.jsp"/>
When the form is first shown ("/edit"), Struts doesn't call reset().
> But, another popular paradigm, going back to the Perl days,
> is to keep submitting back to the same URI. The first time
> the page is retrieved, it is by GET. After that, it is
> submitted back by POST (aka PostBack).
In our case, we can do this with maybe a DispatchAction. Still, it'd
trigger a call to populate the form, which again makes a call to
reset() (to clear those checkboxes) necessary.
<snip/>
> Apparently, Michael wants to do something simliar with Struts
> Dialogs, which seems reasonable to me, if there's a
> reasonable way to do it.
Yeah, I've thought that the reason I'm not understanding Michael is
because the use case is specific for Struts Dialogs. It doesn't seem
to make sense with the usual "show the prepopulated form" + "submit
the user modified form" that I'm used to.
> -Ted.
Hubert
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
