If you have a mechanism of somehow maintaining the session data in your
application context when the session is destroyed, then i dont see a issue in
restoring the same. The HttpSessionListener also has a method sessionCreated.
This method will be called when the session is created. So you can w
Dear gang,
I do not think the issue is how to save the session data, I think the issue is
under what unique identifier the data should be stored. If a session ID is
used to store the data, that ID is only valid for that session. So when a new
session is created the old ID is lost and as such
Now the problem is become more complicated.
Suppose the user is on Page A and clicking on some link here should take him to
Page B. But since the session has expired, the server will first take the user
to the login screen (I am using JBoss/JAAS for authentication). The login
screen appears bec
Ashish,
The flow should occur like this...
| 1 User A is on page 1
|
| 2 User A's session expires
|
| 3 Your session listener is invoked and does some majic to save the session
stored objects
|
| 4 User A requests page 2.
|
| 5 The container determines user A's is not auth
Hi Cgriffith,
Thanks alot for your reply. Please find my reply inline, MARKED AS RED.
The flow should occur like this...
1 User A is on page 1
2 User A's session expires
3 Your session listener is invoked and does some majic to save the
session stored objects.
Ashish,
Your comments are presicely what I have been saying all along. Hence my
statement...
anonymous wrote : I do not think the issue is how to save the session data, I
think the issue is under what unique identifier the data should be stored.
cgriffith
View the original post :
http://www.
