Hello,
I'm using JBoss + Tomcat, but every time that I deploy a new version
of WAR file, all sessions are invalidated... There is any way to
configure JBoss/TomCat to don't invalidate my sessions?
Thanks in advance,
Regis Melo
---
No, you would have to write your own session manager implementation that was an
mbean service deployed outside of the war so that sessions had a scope beyond
that of the war deployment.
--
Scott Stark
Chief Technology Officer
JBoss Group, LLC
What would be the point of hot-deploy then? If you
deploy a new app, how is your session to be accurate
if for example one of the session objects has a new
version behind the object? That is, if you store
Address, and you now extend Address from
AbstractAddress, your old session state object only
I just think that is not a good idea to break down all the user
sessions. Ok, if there is a new version of object thas was in session,
the container could invalidate the session.
Do U really think that is good to work with app that sometimes
invalidate your session? Do U think that Amazon or
Actually, yes, I think they do. Let's make sure we
compare apples to apples. Amazon or other sites would
never deploy a new version of a bean on a working
server in the middle of user requests, most likely
anyway. They'd bring on a new node, or restart one,
while the other nodes were all load
