I recommend not using session, unless it is completely necessary. I
have had memory issues, and other problems like garbage colleciton
when putting information into the session. Basically like one of the
other responders said, just populate your form, do your validation,
and pass it along to another action. In the next form, if you just
want to pass the variables to the next form, just put them into hidden
fields in that form. Still using the same bean, they will get
autopopulated, and so on and so on.

IMOHO it is best to stay away from session information unless it is
something that is necessary for the full site.



On 2/24/06, Chris Cheshire <[EMAIL PROTECTED]> wrote:
> The problem is there is other information in the form bean that is not
> in the page, therefore it is not getting initialised properly.
>
> I am going with the hidden variable approach as suggested.
>
> On 2/24/06, Michael Jouravlev <[EMAIL PROTECTED]> wrote:
> > On 2/24/06, Chris Cheshire <[EMAIL PROTECTED]> wrote:
> > > I have the following chain of events in an app
> > >
> > > ActionA -> PageA -> ActionB -> ActionC
> > >
> > > All transitions are forward requests (not redirects) and PageA ->
> > > ActionB is a POST.
> > >
> > > In ActionA I have a form bean prepopulated with a collection to
> > > display and choose one of in PageA. ActionB then needs to get this
> > > info back out of the form.
> > >
> > > The problem is, since everything is in request scope, once the ActionA
> > > -> PageA forward is completed, the bean is no longer valid. Is there
> > > any way to get the bean to transfer to the next request, or do I need
> > > to use a session bean instead (definitely not ideal as then I have to
> > > put the cleanup for it in numerous places).
> >
> > Since you submit pageA to actionB, the form associated with actionB
> > will be filled out with data from pageA. I don't see what the problem
> > is. Yes, ActionForm will be created again.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

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

Reply via email to