<action-mappings>
<action
path="/Something"
type="app.SelectionAction"
name="selectionForm"
scope="request" <=========== should be scope="session"
validate="false"
>
<forward name="success" path="/pages/p2.jsp"/>
</action>
</action-mappings>
On 4/27/05, Mike Elliott <[EMAIL PROTECTED]> wrote:
> I'm trying to build an application where:
>
> 1) p1.jsp transitions via a link: /do/Something?action=initialize.
>
> 2) This causes class app.SelectionAction to have its execute() method invoked.
>
> 3) The execute() method, based on the parameter, initializes the form passed
> it.
>
> 4) The execute() method then transitions to p2.jsp, which renders the page.
>
> 5) A user changes something, then causes a submit to occur.
>
> 6) The submit transitions via /do/Something?action=update
>
> 7) This causes class app.SelectionAction to have its execute() method invoked.
>
> 8) The execute() method, based on the parameter, stores info from the form.
>
> This is a reasonable scenario, right?
>
> Somewhere between steps 1 and 3, a new form bean is created. This is
> reasonable, I guess. Anyway, it gets initialized in step 3. However,
> somewhere between steps 4 and 8, a second new form is created, losing
> the information so carefully initialized in step 3. I don't want to
> throw away the old bean. I want to keep using the bean I so painfully
> initialized in step 3.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
