http://blog.csdn.net/w2393040183/article/details/50749851
<!-- scan @controller annotations --> < context: Component-scan base-package = " Com.fq.controller " > < context:include-filter type =" annotation " expression =" Org.s Pringframework.stereotype.Controller " /> </ context:component-scan >
It can be seen that the final package should be written, and not write base-package= "Com.fq". This type of writing is scanned for include-filter, not just scanning @controller. hahaha, this needs to be noted. He generally leads to a common mistake, which is that transactions do not work, and the remedy is to add use-default-filters= "false".
(2) The following configurations are available in the Spring-context.xml:
<!-- Configure scan annotations, do not scan @controller annotations Span style= "COLOR: #008000" >--> < Context:component-scan base-package = " Com.fq " > < context:exclude-filter type = "annotation" expression = "Org.springframework.stereotype.Controller" /> </ context:component-scan >
As you can see, he is going to scan all the subclasses under the COM.FQ package, not including the @controller. The problem is that the exculude-filter does not have a scan when the package is not accurate.
The difference between Context:include-filter and Context:exclude-filter in spring