1. In many configurations, the Spring-common.xml and spring-mvc.xml are generally divided into separate configurations, and this configuration on the line of each of the same job, it is particularly clear.
Only scan the @controller in Spring-mvc.xml, as a controller, other things do not do.
In Spring-common.xml, only the annotations of some transaction logic are scanned.
2. The institution that is now given a project package:
Com.fq.controlller
Com.fq.service
Given the two package mechanisms first,
(1) The following configuration is available in the Spring-mvc.xml:
<!--scan @controller annotation-->
<context:component-scan base-package= "Com.fq.controller" >
< Context:include-filter type= "annotation"
expression= "Org.springframework.stereotype.Controller"/>
</context:component-scan>
It can be seen to write the final package, and not to write base-package= "Com.fq". This kind of writing for Include-filter it will scan, not just scan @controller. This should be noted. He generally leads to a common mistake, that is, the transaction does not work, and the remedy is to add use-default-filters= "false".
(2) The following configurations are available in the Spring-common.xml:
<!--Configure scan annotations, do not scan @controller annotations-->
<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 subclasses under the COM.FQ package, not including @controller. For Exculude-filter, there is no problem of scanning after the packet is not accurate.