About no mapping found for HTTP request with URI ...

When you see this blog, it means that you've gone crazy like me! But it's okay. Got it!!!

Those things on the net really look more disturbing, because have not solved ...

Cause 1. The access path is indeed wrong, causing dispatcher to find a place for you to communicate, modify the collar to let him and controller inside the requestmapping just like the line

Cause two: It is also my mistake, is to put Springmvc.xml in their own new folder, but this folder is a Source folder, when in Web. XML <init-param> This is not the case when you configure the value in this way to fail when you start Tomcat:

Classpath*:/sources/springmvc.xml

But there is a problem here (until now, do not know why, do not ask ...)

Workaround: 1. Place the Spring.xml file directly in the SRC directory and configure value to Classpath:springmvc.xml

2. Feel that the first kind of confusion on their own to create a common package such as the name Config, and then configure Value:classpath:config/springmvc.xml

On the line ...

Of course not to say other people's wrong, but it is really I used a long time to come out of the ....

About no mapping found for HTTP request with URI ...