struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "andy wix" <>
Subject Stateless web apps
Date Mon, 23 May 2005 11:18:04 GMT

I am working at a place that doesn't use session state for their web apps.
The reason given is that they have 2 physical servers and 2 Oracle 
Application Servers running on each of these machines for failover.  From 
the little I know about clustering, I thought that if everything in the 
session implements Serializable then session state is tranparently valid 
accross requests - even if you end up on another jvm.

Has anyone else ever heard of this restriction - I can see problems e.g., 
can't use Struts tokens to defeat the usual refresh problems.

More immediately, I have a problem with a typical scenario.  My normal 
approach is:
I have a 'preload' action that gets an ArrayList of data from the db and 
sets this in the session.
Then forward to the jsp that displays this stuff.
This page has something like:

<c:forEach var="wrap" items="${Assignments}" varStatus="status">
  <TD><c:out value="${status.index+1}"/></TD>
    <c:url var="viewApp" value="/">
      <c:param name="indexPos" value="${status.index}" />
          <html:link href="${viewApp}">
            <c:out value="${wrap.applicationVO.applicationName}"/>

This gives me an index of the link that was clicked and in the next action I 
simply look this value up from the ArrayList in the session.

Does anyone know how this functionality could be achieved without using the 


It's fast, it's easy and it's free. Get MSN Messenger 7.0 today!

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message