1. get j1, enter data, submit to s1
2. s1 performs a database retrieval , sets the criteria in session, sets the retrieval result in session, and then forwards to j2.
3. j2 displays the data and allows the user to submit, for one particular item on the screen, a request to s2. Note that j2 is able to display the session data from s1's setAttribute(...).
4. s2 performs database work on behalf of the j2 request and then forwards to either j1 or s1.
Regardless of forwarding to j1 or s1, we loose the session data. This seems like a simple interaction where a session can store useful information, so we're very puzzled why the session seems to disappear.
The object being stored in the session is a java.util.Properties object.
Originally posted by William Brogden:
Are all of these jsp and servlets part of the same web application? Both servlets declared in the same web.xml?
Also - when you store retrieval results in the session, are you storing Strings or something like a ResultSet?