[EMAIL PROTECTED] wrote:
> When a class is reloaded because you have change it the objects saved
> on
> sessions are lost and all the users connected to that application
> suffer
> that.
>
> Do all classes get reloaded or only those that have changed?
>
The details vary by container, but generally the entire webapp is running
under a single classloader, so that all of the classes get dumped and
reloaded.
>
> If all objects in sessions are stable types (e.g. Strings or name/value
> Collections) do we dodge the
> problem?
>
It's not whether they are stable or not that matters, it is whether they
implement Serializable or not. On some containers, such as Tomcat 4.0,
sessions and their Serializable attributes *are* saved across webapp restarts.
>
> ---
> David J.N. Artus
> Consulting IT Specialist, IBM Transarc Lab
> phone: +44 (0) 777 55 22 753 (mobile)
> email: [EMAIL PROTECTED]
Craig
