You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by el...@canada.com on 2002/09/19 14:54:10 UTC
jsp-to-action-to-action: when does the request die
I want to do something this:
(1) (2) (3)
/edit.do ---> JSP ---> /save.do ---> /edit.do
(1) Action '/edit.do' preps and displays the JSP
(does a mapping.finfDorward())
(2) JSP is submitted and POSTs to action, '/save.do'
(3) '/save.do' processes the save and does a
mapping.finfForward() back to '/edit.do' to re-display
the JSP
My question is this: does the request created the JSP
POST die at the first action class or does the second
action class have access to it?
__________________________________________________________
Get your FREE personalized e-mail at http://www.canada.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: jsp-to-action-to-action: when does the request die
Posted by Dave Derry <dd...@acm.org>.
The second action has access to it; if you mean save.do is 1 & edit.do is 2.
If edit .do forwards to somethingelse.do, it also has access to it. The
request 'dies' when the action sends the response to the client.
Dave Derry
----- Original Message -----
From: <el...@canada.com>
> I want to do something this:
>
> (1) (2) (3)
> /edit.do ---> JSP ---> /save.do ---> /edit.do
>
> (1) Action '/edit.do' preps and displays the JSP
> (does a mapping.finfDorward())
> (2) JSP is submitted and POSTs to action, '/save.do'
> (3) '/save.do' processes the save and does a
> mapping.finfForward() back to '/edit.do' to re-display
> the JSP
>
> My question is this: does the request created the JSP
> POST die at the first action class or does the second
> action class have access to it?
>
> __________________________________________________________
> Get your FREE personalized e-mail at http://www.canada.com
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>