The Eclipse project is deployed to the Tomcat path

such as: A Project: D:\javaeclipse\workspace\.metadata\.plugins\org.eclipse.wst.server.core\tmp7\wtpwebapps\A


Description: (1) D:\javaeclipse\workspace\ is Eclipse's current workspace,. Metadata is the directory generated by Eclipse, representing the current D:\javaeclipse\workspace Is Eclipce is the working space.
(2). Metadata\.plugins
is the Eclipse plugin directory, Tomcat is added to eclipse in the form of plugins, so the Tomcat directory of Eclipse is not the real Tomcat installation root
In the Eclipse workspace. Metadata\.plugins\org.eclipse.wst.server.core
(3) As for TMP7, it's a tomcat in eclipse new
Server, a tmp1,2 server is created under the core TMP1 and tmp2 ... And so on, I built 7 tomcat
Server, so there will be TMP7, and my A is deployed under this TMP7. Here's TMP7
Represents a temporary tomcat (the directory structure inside is a bit like the directory structure under the Tomcat installation path, which can be understood as a Tomcat replica, I guess TMP is a temporary meaning.) ）
(4) Wtpwebapps
Typically, when we manually deploy a project with Tomcat, there are 2 publishing locations for the project: 1 refers to the path to the specified WebApp in the configuration file in Conf, which is the Web project path, which
Development to deployment is the same directory of files, not copied or packaged; the 2nd is to package the Web project into a war package to copy to the {Tomcat_home}/webapps directory
, Tomcat automatically recognizes the war package, extracts the war package to get a Web project, and generates the relevant JSP file to D:\javaeclipse\workspace
\apache-tomcat-6.0.37\work\catalina\localhost (note that under localhost is just web files, not all project files, all the files should go to WebApps under Search),
The trouble with publishing this way is to re-pack the project and put the new war package under the WebApps, even if you just modify a text or identifier on a JSP file and re-
Generate a war package to publish (the war includes a suffix to rar to view the contents of the content, but modify the inside of the file to change back to the war suffix as if it can not be identified by Tomcat, this is not known, not sure, to be tested to know)
And here the Wtpwebapps, should be equivalent to the actual Tomcat WebApps directory, Wtpwebapps in a equivalent to WebApps under the A.war generated a project, should be saved to generate war package copy to WebApps directory operation.
In other words, the project's release file is in the tomcat-wtpwebapps\a of this webapps\a or eclipse configuration. The browser requests access to write a folder, not our eclipse work
As a real engineering document in the space workspace.

This explains why Eclipse compiles a jsp/js or Java file in the Web project after Eclipse modifies it (building,
There is no release project Eclipse will recompile the project, unrelated to Tomcat, this is Eclipse's self-checking feature, and then publish
To the eclipse-configured Tomcat, which is publish to Wtpwebapps.
(If Eclipse does not configure Tomcat, but instead manually publishes a, then after Eclise executes building, we will regenerate the war package to overwrite
Tomcat_home\webapps under the Old war package, Tomcat will monitor the war package changes and republish the Web project before the browser can request a new
JSP or servlet. Of course, if you are using a
Tomcat_home\conf\server.xml configuration of the way released, it is much easier, eclise on the modified, building completed, Tomcat
will automatically republish this project A. A generic Web application server, such as Tomcat
JBoss resin should have the ability to re-publish the project automatically. ）

The Eclipse project is deployed to the Tomcat path