RE: [wtp-dev] how is context reload triggered by WTP?
Usage questions such as this are best asked on the WTP newsgroup (see: http://www.eclipse.org/newsgroups/index.php). This mailing list is for issues pertaining to the development of WTP.
This Context reloading is being done by Tomcat. It is a consequence of having reloadable="true" in the Contexts for added projects found in the server.xml under the Servers project in your workspace. Change the value to "false" in the server.xml or change it using the Modules tab of the Server Editor and this behavior will stop.
From: wtp-dev-bounces@xxxxxxxxxxx [mailto:wtp-dev-bounces@xxxxxxxxxxx] On Behalf Of Toomas Römer
Sent: Thursday, July 17, 2008 11:14 AM
Subject: [wtp-dev] how is context reload triggered by WTP?
I have Eclipse, WTP and I've configured a server. Tomcat 6. I have
enabled automatic publishing (actually all the settings are default).
I change a servlet and a context reload will happen.
Jul 17, 2008 5:27:45 PM org.apache.catalina.core.StandardContext reload
INFO: Reloading this Context has started
I've searched the WTP sources as what exactly triggers the reload. I
have not found it. A find -mmin 1 in the catalina base shows that a
public/publish0.dat, conf/server.xml and my servlets have been copied.
So the reload is not tiggered by touching the web.xml but
programmatically somwhere. Could somebody tell me where does the
tirggering take place?
Why am I interested? There have been couple of posts about wanting to
disable the context reload but still copy the assets of the project
and I'm looking into how to implement this.
wtp-dev mailing list