?This doesnt sound right.
Its just an http request. It shouldn't lose anything except session data.
The container should route the http request and all the request items from
the form.
thanks,
Mike

----- Original Message -----
From: "David Graham" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, December 04, 2002 3:03 PM
Subject: Re: Request losing data after container security check


> If the session times out then you probably want the user to go back to the
> start page anyways.  Request data is only stored by the container long
> enough to complete a request for one page so it won't be around after that
> request.
>
> David
>
>
>
>
>
>
> >From: "Michael Lee" <[EMAIL PROTECTED]>
> >Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
> >To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
> >Subject: Request losing data after container security check
> >Date: Wed, 4 Dec 2002 14:27:16 -0500
> >
> >I have a screen a.jsp that calls a.do which then forwards to b.jsp
> >I have a form called AForm.java. I have a field called email in
AForm.java.
> >In a.jsp a user can set email, call a.do and then forward to b.jsp which
> >does a <bean:write name="aForm" property="email"/>. This works just fine
> >and outputs the email.
> >Problem is, if the session times out (15 mins) then the user is required
to
> >log back in. If the data is entered on a.jsp and the session times out
and
> >the user clicks submit, then when it gets to b.jsp it doesn't have any
> >data? In the struts config a.do is of scope="request". I would think that
a
> >request would keep that data unlike scope="session".
> >I want to keep the data upon submit, even if the container wants to
> >validate the user.
> >thanks,
> >Mike
>
>
> _________________________________________________________________
> The new MSN 8: advanced junk mail protection and 2 months FREE*
> http://join.msn.com/?page=features/junkmail
>
>
> --
> To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
>

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to