1)store in db
2)if static.. place in properties file
3)you can use OGNL to place values into 'application' scope

surest and safest is to store in db..

Mit freundlichen Grüßen
Martin 
______________________________________________ 
Disclaimer and confidentiality note 
Everything in this e-mail and any attachments relates to the official business 
of Sender. This transmission is of a confidential nature and Sender does not 
endorse distribution to any party other than intended recipient. Sender does 
not necessarily endorse content contained within this transmission. 




> 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 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.
> 
> As this is a common task, there must be a design pattern.
> 
> Thank you in advance!
> 
> ~Andreas
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
> For additional commands, e-mail: user-h...@struts.apache.org
> 

_________________________________________________________________
Windows Live™: E-mail. Chat. Share. Get more ways to connect. 
http://windowslive.com/explore?ocid=TXT_TAGLM_WL_t2_allup_explore_012009

Reply via email to