tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Remy Maucherat" <>
Subject Re: TC 4.0.1: classes being cached - requires restart to update
Date Fri, 09 Nov 2001 22:08:16 GMT
> --- You wrote:
> Could you please try Remy's test case?
> > thanks,
> > brett
> >
> Craig
> --- end of quote ---
> ah, actually i hadn't realized Remy was suggesting that i try what he had
as a
> test case, ok.
> I did modify the jspcalendar bean class and did find that the log did show
> webappClassLoader noting that the resource was modified -- _only after i
> the class by hand_ -- saving the source file change was not enough. then
> reloading the jsp reflected the change.
> but I change my class and recompile and no such notification to the log,
> change to the jsp output, until i have the manager reload the context,
> combo, which is much better than a restart of tomcat, rebuild class by
> reload context does make the change show up.

Ok, I'll look at it. You'll always have to recompile manually the class
files, though.

> I have not noticed that waiting 15 secs helped anything. manual reload did
> trick.
> Tom Drake had suggested my class had session context, if by that he means
is the
> class using session variables, no, but the jsp that is importing the class
> so overall the compiled servlet wouldbe using session elements. perhaps
this is
> my difficulty. I need to use the session attributes to maintain state


To unsubscribe:   <>
For additional commands: <>
Troubles with the list: <>

View raw message