How to prevent Context Reload upon changing web.xml

[Neeraj Vora]

I migrated from Tomcat 4.0.2 to Tomcat 5.5.7. The former was not reloading 
the context if I changed application’s 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 set 
to false does not prevent Tomcat from reloading the WebApp upon touching the 
web.xml.

TIA.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Charset in Content Type: Tomcat 4 versus Tomcat 5

[Neeraj Vora]

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
Now with Tomcat 5.5.7, following is the header.
Content Type: application/x-java-jnlp-file;charset=iso-8859-1
MS IE has an unfortunate bug whereby it cannot associate this with Java Web 
Start. This has been documented as KB 871248. I tried 
response.setCharacterEncoding(null) but it does not take out the trailing 
charset. Is it possible somehow to still have Tomcat 5.5.7 return the header 
that Tomcat 4.0.2 used to?

TIA.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]