ck Reumann" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List"
Sent: Saturday, February 25, 2006 12:11 PM
Subject: Re: passing objects from one request to another
> [EMAIL PROTECTED] wrote:
> > Rick,
> >
> > It sounds like you are having a problem that I so
[EMAIL PROTECTED] wrote:
Rick,
It sounds like you are having a problem that I solved last week.
Actually, I'm not the one having the problem. I was just replying to the
initial post, that I'd use the Session for stuff that needs to accessed
across multiple requests.
I had a situation wher
On 2/24/06, Jim Reynolds <[EMAIL PROTECTED]> wrote:
> 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 populat
Users Mailing List
Sent: Fri, 24 Feb 2006 21:41:11 -0500
Subject: Re: passing objects from one request to another
> Jim Reynolds wrote:
> >
> > IMOHO it is best to stay away from session information unless it is
> > something that is necessary for the full site.
>
>
Jim Reynolds wrote:
IMOHO it is best to stay away from session information unless it is
something that is necessary for the full site.
imo, the Session is better than using hidden variables. People freak out
over using the Session like it's something taboo. If it's a trade off
between compl
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 anothe
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]
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 collecti
Chris Cheshire wrote the following on 2/24/2006 5:31 PM:
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 instea
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
10 matches
Mail list logo
