Reprint: http://blog.csdn.net/tianlincao/article/details/7263840
Before each modification of the class file, after saving Tomcat will need to automatically restart, today after the set up, can support the hot deployment, and online information is diametrically opposed!
My environment:
Eclipse version 3.4, set to auto-compile by default (Project-biuld automatically hook)
Tomcat version 6.0, server.xml settings are as follows:
[HTML]View Plaincopy
- <host appbase= "WebApps" autodeploy= "true" name= "localhost" Unpackwars= "true" xmlnamespaceaware=" false " xmlvalidation=" false ">
- <Context docbase="Cpcweb" path="/cpcweb" reloadable="true" source=" Org.eclipse.jst.j2ee.server:CPCWeb "/></Host>
You can see the Host tag and the context tag
Autodeploy= "true"----automatic deployment
Reloadable= "true"----automatically loaded
Now I have both values set to False, that is, the modified configuration is as follows:
[HTML]View Plaincopy
- <Host appbase="WebApps" autodeploy= "false" name="localhost" unpackwars=" True " xmlnamespaceaware=" false " xmlvalidation=" false ">
- <Context docbase="Cpcweb" path="/cpcweb" reloadable= "false" source=" Org.eclipse.jst.j2ee.server:CPCWeb "/></Host>
Reboot tomcat, support automatic loading of classes, Tomcat does not restart, console print less, the world is finally quiet ...
About the hot deployment and hot load of Tomcat 6