Tomcat server was configured properly in eclipse, and the Eclipse build Tomcat service was built in the server view, where new server was created, but after the project was deployed to Tomcat, the Tomcat home page reported 404 errors. Then I looked at Tomcat's WebApps and didn't find the project I was deploying, but since I didn't deploy it to my tomcat, why would I be able to access the project normally? The original use of the new server is the default of eclipse with Eclipse, so I started Tomcat server, entered my own Tomcat home address actually access the eclipse comes with the Tomcat server, So it's not normal to find it, but after some thought, how it accesses the project I'm deploying, explaining the next paragraph.
This is the Eclipse optimization, it will copy the Tomcat configuration files to their own a hidden directory, when you start with eclipse, it is not to start the startup of Tomcat, but Eclipse's own copy of the heap configuration file, So, when you start with Eclipse, accessing the home page of Tomcat comes out 404.
. metadata\.plugins\org.eclipse.wst.server.core\tmp1
This is the directory where the default copy configuration file for Eclipse is stored.
So since eclipse comes with Tomcat just copied its Tomcat profile, it won't be able to access the Tomcat home page.
So that's a lot of solutions?
In the server view, double-click the Tomcat server, go to the edit window, see an option called Server location, by default the first item (that is, use workspace metadata) is selected. Modify this to the second option (use Tomcat installation), restart Tomcat again, and you will have normal access to http://localhost:8080, and if this option is grayed out, remove all items under Tomcat , and clean tomcat.
Tomcat is started in the Tomcat directory, with normal access to the Tomcat home page, but with Tomcat integrated in eclipse but not the Tomcat home page, access to the published project