How do you prevent the session from filling up with junk from previous
screens? Or to put it another way:
I have written some screens that have to store the form bean in the
session scope as each screen is interconnected and uses the same
instance of the form bean. If I change the scope to
or replace it all at once. Have to e.g. prepend key
with user information(getSessionID()) to get same bean for user back?
Greets Jörg
-Original Message-
From: julian green [mailto:[EMAIL PROTECTED]
Sent: Freitag, 07. März 2003 10:33
To: Struts Users Mailing List
Subject: How do you keep your
(getSessionID()) to get same bean for user back?
Greets Jörg
-Original Message-
From: julian green [mailto:[EMAIL PROTECTED]
Sent: Freitag, 07. März 2003 10:33
To: Struts Users Mailing List
Subject: How do you keep your session junk free?
How do you prevent the session from filling up with junk from
(getSessionID()) to get same bean for user back?
Greets Jörg
-Original Message-
From: julian green [mailto:[EMAIL PROTECTED]
Sent: Freitag, 07. März 2003 10:33
To: Struts Users Mailing List
Subject: How do you keep your session junk free?
How do you prevent the session from filling up
Over on another mailing list I'm on the consensus is that
continuation-style programming is much better than the present
approaches suggested by struts and other frameworks. In particular,
they solve the back button/refresh type problems much more cleanly
than other languages/frameworks.
As a
On Fri, 7 Mar 2003 10:34:13 -0500
Sundar Narasimhan [EMAIL PROTECTED] wrote:
Over on another mailing list I'm on the consensus is that
continuation-style programming is much better than the present
approaches suggested by struts and other frameworks. In particular,
they solve the back
Explain how some other approach handles it in any better way? Use of
token to prevent duplicate submissions works for me. And what do you
mean by a continuation-style programming?
The token approach is an easy solution. One of the sites listed was a
Smalltalk web framework. It's good to look
Maybe what we need is an abstraction over the current request
mapping stuff. If you think about it, what Struts basically does is
mapping a request from a browser to some class that then executes a
method (I know Struts has a lot more things, but this is the main one).
Maybe we could go a
It would be neat if you could group a bunch of action definitions
together and have the form bean persist while the group remianed active.
Julian
David Graham wrote:
Explain how some other approach handles it in any better way? Use of
token to prevent duplicate submissions works for me. And
I was thinking exactly about that... usually you could identify that
bunch of actions as steps inside an use case of the system. The data
collected inside that use case usually is useless outside that use case
and is usually used to make a call to business logic sitting in EJBs, or
business
Subject: Re: How do you keep your session junk free?
It would be neat if you could group a bunch of action definitions
together and have the form bean persist while the group remianed active.
Julian
David Graham wrote:
Explain how some other approach handles it in any better way? Use
El vie, 07-03-2003 a las 13:00, Jose Gonzalez Gomez escribió:
Please, don't take this as criticism to Struts. I think Struts is a
great framework and I'm using it and will be using it in whatever J2EE
project I do, but maybe we could start thinking a level above... what do
you think?
List
Subject: Re: How do you keep your session junk free?
I kinda have a class that does that if you want.
I have an Action called ChainAction that can call N number of
actions in a
row and passes the same form and request info through all the actions.
The last action in the chain
Explain how some other approach handles it in any better way? Use of
token to prevent duplicate submissions works for me. And what do you
mean by a continuation-style programming?
Hi, Rick: CPS is a commonly accepted idiom for representing what a
program does next in your language. Some languages
On Fri, 7 Mar 2003 14:03:08 -0500
Sundar Narasimhan [EMAIL PROTECTED] wrote:
Explain how some other approach handles it in any better way? Use of
token to prevent duplicate submissions works for me. And what do you
mean by a continuation-style programming?
Hi, Rick: CPS is a commonly accepted
On Friday, Mar 7, 2003, at 14:16 US/Eastern, Rick Reumann wrote:
Very interesting, thanks for the information. Can this kind of behavior
be achieved though simply by hitting a browser back button? I
wouldn't
think that would be possible without using javascript to resubmit the
page or to make
-
From: Joe Barefoot [EMAIL PROTECTED]
To: Struts Users Mailing List [EMAIL PROTECTED]
Sent: Friday, March 07, 2003 2:00 PM
Subject: RE: How do you keep your session junk free?
Does this model include a means of managing the session objects (I would
assume yes, but didn't see anything to that effect
topic... but I figured it might be of
interest to
someone...
--
Sloan
- Original Message -
From: Joe Barefoot [EMAIL PROTECTED]
To: Struts Users Mailing List [EMAIL PROTECTED]
Sent: Friday, March 07, 2003 2:00 PM
Subject: RE: How do you keep your session junk free?
Does
Subject: RE: How do you keep your session junk free?
Interesting. We are less concerned about work flow that being able to
create wizards using session objects, and have them cleaned up in a timely
fashion. I think it's nice to be able to manage extra parameters via the
actionMapping as you
19 matches
Mail list logo
