This is the million dollar question! Always strive to "hold onto" the least amount of data possible. This usually means for as long as it takes to build the web page. Use the request scope unless you *must* access the *same* data later. At which point you should save only *keys* to the actual data in session or some longer lasting scope. Using the session like a data store will severely limit your scalability and performance.
Scott On Thu, Oct 16, 2008 at 4:28 PM, John Cartwright <[EMAIL PROTECTED] > wrote: > Hello All, > > What is the recommendation for sharing data between actions? I have one > action that performs a search and displays the results in a JSP page. That > results page contains links to another action in which I'd like to have > access to the original search results. My first instinct was to reach for > the HttpSession, but I understood that approach was discourages in S2. > > Can anyone offer me some advice on the subject? > > Thanks! > > -- john > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
