Title: RE: ServletSession's and Servlet Reloading
Also,
I want to emphasize that the solution mentioned is not desirable.
Maintaining session information even after reloads promotes rapid
development. It allows one to build up a session and then work on a single
servlet, compiling
Title: RE: ServletSession's and Servlet Reloading
Actually, it is possible. Session's are not lost
in Websphere when you recompile any of the classes... servlet or
otherwise. I'm not reloading the session, just a single servlet (which of
course can access the session). No,
Title: RE: ServletSession's and Servlet Reloading
This behaviour actually makes a lot of sense when you consider how classloaders work in java. It is impossible to throw away any given class, in order to do ANY reloading of anything at all, you need to throw away the classloader, and m
I do have development=true but that's only so that orion generates the
source for the jsps as far as I know.
I ran a few tests to see what was happening and I got mixed results. The
most disturbing was the code below. It simply keeps track of an attribute
in the session and how many times it ex
bject: ServletSession's and Servlet Reloading
>
>
>
> Orion 1.1.37 (as well as all other versions as far as I remember) lose the
> Servlet Session whenever a servlet is reloaded.
>
> Why is this? Is this an issue with how classloaders are used? This makes
> working wi
Orion 1.1.37 (as well as all other versions as far as I remember) lose the
Servlet Session whenever a servlet is reloaded.
Why is this? Is this an issue with how classloaders are used? This makes
working with complex sessions very difficult to test and debug since each
time I recompile a servl
