on 6/13/2000 2:55 PM, Sean Legassick at [EMAIL PROTECTED] wrote:
> Jon particularly (when you finally plough through all your emails to
> here),
>
> The last changes you committed to do with making all session objects
> serializable did the trick on JServ. Now logins persist through reloads
> every time, which is great. I double-checked with some older jars, and
> it definitely didn't work a couple of weeks ago.
>
> Having had an easy time with that I thought I'd take the opportunity to
> bite the Tomcat bullet. I had a problem with the latest CVS tomcat (see
> other email), but when I worked around that I found that indeed logins
> weren't peristing through reloads :-(
>
> But at least the serialization seems to be sorted out, so it *can* work.
> If I get a chance I'll look some more at what's going on - a good chance
> to learn more about Tomcat anyway.
>
> Sean
Cool! That is good news. That puts the blame back into Tomcat which is nice
since that is also my code that must be failing or close to it. Ok, this
will be easier to debug now. I will try to get to it tomorrow
I have a felling that after the handleReload() method in Tomcat is called,
the sessions are still getting nullified somewhere.
-jon
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
