Spring Component Scan异常：EAR中模块依赖注入及控制器注册问题

Alright, let's tackle your problem head-on—you're stuck between two frustrating scenarios: either your service bean won't inject, or your controller isn't registered. Here's why this is happening and how to fix it:

First, a Critical Mistake: Annotating Interfaces with @Component #

You mentioned your IBaseService interface has a @Component annotation, but that's not how Spring works. Spring can't instantiate interfaces—only concrete implementation classes should be marked with @Component (or better, @Service for service-layer beans). That's one big reason you're getting the NoSuchBeanDefinitionException—Spring can't find a usable instance of IBaseService.

Second, Spring Web Context Hierarchy Matters #

In a Spring web app (especially in an EAR setup), you have two separate contexts:

• Root Context: Managed by ContextLoaderListener, this holds your business/service/DAO beans (from your Business JAR).
• DispatcherServlet Context: This is a child context that only handles MVC components (controllers, view resolvers, etc.). It can access beans from the root context, but the root can't access its beans.

Your current setup only uses the DispatcherServlet context, which causes the conflicting issues:

• Scanning com.test.project tries to load everything, but fails to find a valid IBaseService bean (thanks to the interface annotation mistake, plus context boundaries).
• Scanning only com.test.project.service loads your service beans but misses the controllers, hence the 404.

Step-by-Step Fixes #

1. Correct Your Service Annotation #

Remove @Component from the IBaseService interface, and add @Service to its concrete implementation:

// IBaseService (no annotation needed here)
public interface IBaseService {
    void postData(String request) throws CustomException;
}

// Concrete implementation
@Service
public class BaseServiceImpl implements IBaseService {
    @Override
    public void postData(String request) throws CustomException {
        // Your business logic here
    }
}

2. Split Your Spring Configs #

Create a root context config (applicationContext.xml) in your WAR to load business beans from the Business JAR:

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
       xmlns:context="http://www.springframework.org/schema/context"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="
           http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd
           http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context.xsd">

    <!-- Scan only service packages from your Business module -->
    <context:component-scan base-package="com.test.project.service"/>
    <context:annotation-config/>
</beans>

3. Update dispatcher-servlet.xml to Focus on Controllers #

Modify your MVC config to only scan controller classes—this avoids context conflicts and ensures controllers are registered:

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
       xmlns:context="http://www.springframework.org/schema/context"
       xmlns:mvc="http://www.springframework.org/schema/mvc"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="
           http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd
           http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context.xsd
           http://www.springframework.org/schema/mvc http://www.springframework.org/schema/mvc/spring-mvc.xsd">

    <!-- Scan only your controller package -->
    <context:component-scan base-package="com.test.project.controller"/>
    <mvc:annotation-driven/>
</beans>

4. Configure web.xml to Load Both Contexts #

Update your WAR's web.xml to register the root context listener and link it to your new config:

<web-app xmlns="http://xmlns.jcp.org/xml/ns/javaee"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/web-app_4_0.xsd"
         version="4.0">

    <!-- Load Spring Root Context -->
    <context-param>
        <param-name>contextConfigLocation</param-name>
        <param-value>/WEB-INF/applicationContext.xml</param-value>
    </context-param>
    <listener>
        <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
    </listener>

    <!-- DispatcherServlet Configuration -->
    <servlet>
        <servlet-name>dispatcher</servlet-name>
        <servlet-class>org.springframework.web.servlet.DispatcherServlet</servlet-class>
        <init-param>
            <param-name>contextConfigLocation</param-name>
            <param-value>/WEB-INF/dispatcher-servlet.xml</param-value>
        </init-param>
        <load-on-startup>1</load-on-startup>
    </servlet>
    <servlet-mapping>
        <servlet-name>dispatcher</servlet-name>
        <url-pattern>/</url-pattern>
    </servlet-mapping>
</web-app>

Final Checks #

• Make sure your Business JAR is properly included in the EAR and that the WAR has a dependency on it (verify your application.xml if you're using one).
• Double-check that your controller class is in the com.test.project.controller package (or whatever package you specified in the dispatcher-servlet scan).
• Confirm that BaseServiceImpl is present in the Business JAR and has the @Service annotation.

内容的提问来源于stack exchange，提问作者Vinay Vullakula