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
