Go: Solve the problem of setting property ' source ' to ' org.eclipse.jst.jee.server

I found this problem online search, found the address is: http://blog.csdn.net/z69183787/article/details/19911935. But there was a "turn" on his headline, and I didn't find the original author, For the time being, just mark the site you found.

This is the problem I met on the night of September 4, 2013, I did not sleep for this problem all night!
For this problem, I believe my method has been able to help 90% of people solve!
When you run the Web project with Eclipse, you will see the console appear:
WARNING: [Setpropertiesrule]{server/service/engine/host/context} Setting Property ' source ' to ' Org.eclipse.jst.jee.server:firstProject ' did not ' find a matching property.
Such words, said the Server.xml service tag in the engine tag in the host tag in the context tag configured a ' Source ' property, the property value is ' Org.eclipse.jst.jee.server: Firstproject '.
But the problem is that the context tag is not supported by the Source property, so we jumped out of the warning, so we also found that despite the warning, but most people's program is still able to run without problems, but a few people can not run.
Maybe you've got a lot of questions on the Internet, and there's a solution, but you did it the way you did, and the warning is still there!
Now you can follow my steps to do it:

Let me first talk about the steps that people say on the internet, bury a foreshadowing
1. Double-click Tomcat v7.0 at localhost in servers

2. Then jump out of the interface:

See, in the Server options option there is a publish module contexts to separate XML files option, here we also hook up, but the problem is not so must solve, I said some friends do, The problem is still unresolved, remember to save the tick, if the warning still exists friends follow me continue to look down.

3.

People carefully compare your own and my picture, you will find that your default option should be Use workspace metadata this option, but the author I changed the installation path of Tomcat, because use Workspace path folder is not easy to find in the following explanation of the file, so I use the 2nd Tomcat installation directory to operate, and deploy path: If you have not changed, it should be called Wtpwebapps, because before writing the article, I've got rid of it and I don't know if it's the name, but the point is that it's definitely not webapps, so the reader will do the following based on the value of their deploy path.
Well, ready to work almost, now is the point, why a lot of people do 1.2 steps after the good and your own not good?
The reason is that you have run the process sequence before you do 1 2 steps, and the program will have one more backup folder under the Tomcat folder before running

The directory structure inside

There is no familiar feeling, yes this is the file that was copied from the Conf folder in the Tomcat directory.
The next step is to say the operation is good:
4.
Delete just the backup folder [backup location according to the 3rd step, because the author uses the Tomcat installation directory so it is directly found in the directory, but if you use workspace metadata This option, you are in the \ Workspace\.metadata\.plugins\ Org.eclipse.wst.server.core path can see there are a lot of files, Eclipse will publish the project here, inside the directory structure and Tomcat inside the similar, in short, put \workspace\.metadata\. Plugins\org.eclipse.wst.server.core all the files inside the file are erased.
5.
Find the Catalina directory in the Conf directory in the Tomcat directory with a localhost folder and delete all the files in the folder.
6.
Here we tell you that the 3.4.5 step is simply to tell you the details of the eclipse release, and deleting the file above is not really a hassle:
In servers Tomcat v7.0 at localhost, first right---remove all the projects that have been added, then right--->clean the files in the project's virtual directory and then rerun your program.

Note: If someone wants to change the project publishing directory in the 3rd step server locations As I do, you will notice that the options in the server locations are gray, not changed, and this requires you to follow the removal item in step 6th. Empty the file, and then you are surprised to find that the server locations can be modified, OK, tired, I went, wrote for 3 hours, hoping to help you solve your problems, see you!!!!

I personally experienced the problem solved according to 1,2,3,4,5 department.

Go: Solve the problem of setting property ' source ' to ' org.eclipse.jst.jee.server