struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "MADISHETTY, ASHOK [AG-Contractor/8042]" <>
Subject RE: problem in writing scope="session" in actionMappingDefination
Date Mon, 04 Sep 2006 09:22:13 GMT


As you know that request scope attributes only live for the life of 1
request. Attributes in session scope are shared across every request a
specific user makes.  


However, I googled and found a link. Please see under Put the list in
Session scope in the below link as it may answer your question:








-----Original Message-----
From: Parvat Singh Ranawat [] 
Sent: Monday, September 04, 2006 2:26 PM
To: Struts Users Mailing List
Subject: problem in writing scope="session" in actionMappingDefination


Hi All,


I wanted to know what are the drawbacks of using

SCOPE= "session" in place of "request" in actionMappingDefination


  <action name="formName"  type="ActionName"

 validate="false" parameter="action" scope="request"



Is it all depend upon our requirement or it is good practice to use

scope="request" in place of session

as if we do so it ll take lot of memory to store list of data in the

sessionScope that may be avoided


please do give me some suggestions as in my application some work can be

accomplished by keeping scope="session"

and i can do the work by keeping scope="request" but some additional code is

required to do that .........


so should I go with scope="session" or not




Shakti Singh

This e-mail message may contain privileged and/or confidential information, and is intended
to be received only by persons entitled to receive such information. If you have received
this e-mail in error, please notify the sender immediately. Please delete it and all attachments
from any servers, hard drives or any other media. Other use of this e-mail by you is strictly

All e-mails and attachments sent and received are subject to monitoring, reading and archival
by Monsanto. The recipient of this e-mail is solely responsible for checking for the presence
of "Viruses" or other "Malware". Monsanto accepts no liability for any damage caused by any
such code transmitted by or accompanying this e-mail or any attachment.

  • Unnamed multipart/alternative (inline, 7-Bit, 0 bytes)
View raw message