Andreas Joseph Krogh wrote:
> On Wednesday 24 January 2001 13:59, you wrote:
> > The scenario is... while running a Struts app on Tomcat 3.2 with the
> > nightly build from last night (20010123), recompile one of the classes in
> > the WEB-INF/classes directory, try to continue running the app (that is,
> > hit a button or link in the app) The result, for me, is always a thrown
> > exception of some kind. This happens regardless of whether there was any
> > significant change to the recompiled class or not.
> >
> > Clearly Tomcat is detecting the changed class and is doing something,
> > presumably reloading the app. I would expect that one would be able to
> > continue with the app (presuming that the changes to the class were not
> > drastic) But, instead, I must always stop and start Tomcat and reenter the
> > app from the beginning.
> >
> > Craig has made it clear that Tomcat will reload the app if it detects
> > changes, and that seems to be happening. I expected that this capability
> > meant I could do hot reloads of the app, but this isn't the case. I could
> > use some clarification of what might be going on here. Thanks.
> >
> > Will
>
> I have the same problem, it throws
> javax.servlet.ServletException:
> org.apache.struts.util.PropertyMessageResources
>
> It seems the classloader has problems reloading the struts.jar for some
> reason. I would really appreciate an answer to this so I can go on being
> productive again:-)
>
This morning I applied a patch that may help ... the PropertyMessageResources
object was not completely serializable. Please try it again with tonight's
nightly build.
There may well be other issues with Tomcat 3.2 not always detecting changes in
non-servlet classes, and possibly not cleanly restarting the app. These are
among the reasons that the internal approach to reloading used in Tomcat 4.0 is
totally different.
>
> --
> Andreas Joseph Krogh <[EMAIL PROTECTED]>
Craig
