I migrated from Tomcat 4.0.2 to Tomcat 5.5.7. The former was not reloading
the context if I changed applications web.xml file after deployment. The
latter does that. Is there a way to prevent it? During the searching for
this I read a post that having a context entry with reloadable attribute
Hello World,
I migrated from Tomcat 4.0.2 to Tomcat 5.5.7 which is quite nice for me but
a not so good thing happened as a side-effect due to a MS bug. A particular
response within my application had the following content-type header in
Tomcat 4.0.2
Content Type: application/x-java-jnlp-file