Re: [S2] Store a request and invoke it later

2009-01-30 Thread Andreas Mähler
Hello Ralf, sorry for not replying earlier. I have to check the list more frequently. Ralf Fischer schrieb: Hint: storing *everything* into the session might be unwise in some circumstances, as all resources on a server are limited, even cheap memory. everything == "everything that is necess

Re: [S2] Store a request and invoke it later

2009-01-24 Thread Ralf Fischer
Hi Andreas, Am 25.01.2009 um 02:53 schrieb Andreas Mähler: Thank you, Dave. I think Martin misunderstood me. I was planning to store everything in the session anyway. What I would like to know is _what_ I have to store and _how_ to invoke the right action later in order to make the login

Re: [S2] Store a request and invoke it later

2009-01-24 Thread Andreas Mähler
Thank you, Dave. I think Martin misunderstood me. I was planning to store everything in the session anyway. What I would like to know is _what_ I have to store and _how_ to invoke the right action later in order to make the login stuff transparent. Maybe I am also going to check out Spring S

Re: [S2] Store a request and invoke it later

2009-01-21 Thread Dave Newton
Martin Gainty wrote: 1)store in db 2)if static.. place in properties file 3)you can use OGNL to place values into 'application' scope ... 3) Seems like 'session' would be more appropriate since we're talking about storing an individual user's request, to be re-used after a login. And it woul

RE: [S2] Store a request and invoke it later

2009-01-21 Thread Martin Gainty
> To: user@struts.apache.org > From: andreas.maeh...@stud.uni-karlsruhe.de > Subject: [S2] Store a request and invoke it later > Date: Thu, 22 Jan 2009 02:35:49 +0100 > > Hello everybody, > > I would like to know if there is a sane way to store a request (i.e. > action name

Re: [S2] Store a request and invoke it later

2009-01-21 Thread Wes Wannemacher
On Wednesday 21 January 2009 20:35:49 Andreas Mähler wrote: > Hello everybody, > > I would like to know if there is a sane way to store a request (i.e. > action name and all parameters) and use it later. > > It would be nice to do this to redirect a user to the login screen and > just invoke the or

[S2] Store a request and invoke it later

2009-01-21 Thread Andreas Mähler
Hello everybody, I would like to know if there is a sane way to store a request (i.e. action name and all parameters) and use it later. It would be nice to do this to redirect a user to the login screen and just invoke the original action after the user has been successfully authenticated.