"Frances" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> thank you very much Larry.. oh brother, my boss insists there's a way..
> there HAS to be a way.. how can a servlet container be designed that only
> reloads servlets when you restart it? ok, thanks again...
>
You shoul
thank you very much Larry.. oh brother, my boss insists there's a way..
there HAS to be a way.. how can a servlet container be designed that
only reloads servlets when you restart it? ok, thanks again...
Larry Isaacs wrote:
I has been quite a while since I have used Tomcat 3.3.x.
My recol
I has been quite a while since I have used Tomcat 3.3.x.
My recollection is that accessing the changed servlet would
trigger a reload of the webapp. This differs from the newer
Tomcats which have a background thread checking for changes.
Also, with a default configuration, I don't recall anything
Frances wrote:
when I make changes to a servlet I don't see changes unless I turn
tomcat off and on... this is a huge pain, it's at work, where we can't
be turning Tomcat off and on all day long whenever we make changes to a
servlet.. Is there a way around this? (Does Tomcat 3 come with a
M
