Desarrollo wrote:
>
> hi...
>
> the sessions objects will not survive a reload of classes.
> objects that manage persistence between client request will dead.
> Then all the users will lost their objects in the server side.
>
> Exist a simple way to manage this problem
> In a production environment is a very big problem.
Change to a better server? My project uses JRun 2.3.1. I just ran a quick test
where I made a request to a servlet which stored an object in the session. Then
I modified the servlet, copied it into the servlets directory. The next request
to the servlet caused the servlet to be reloaded, and the object was still in
the session. So, JRun 2.3.1 does persist session objects across class reloading.
If your server does not do this, then one way to resolve the problem is to keep
a reference to all sessions; you could write a class to do that, and to
serialize and deserialize all session objects to and from a persistent store.
K Mukhar
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
