Spring创建Bean报错（自动装配问题）：Maven多模块项目新手求助

Hey there, let's tackle this autowiring issue you're facing with Spring bean creation—super common when starting out with multi-module Maven projects, so don't worry! Here are the step-by-step checks and fixes I'd recommend:

1. Ensure Backend Module Beans Are Scanned by Spring #

First off, double-check that your DAO and Service classes in the backend module have the right Spring annotations:

• Add @Repository to DAO classes
• Add @Service to Service classes

Then, make sure your frontend module's Spring configuration (either JavaConfig or XML) includes the backend package in component scanning. For example:

JavaConfig example: #

@ComponentScan(basePackages = {"com.yourproject.frontend", "com.yourproject.backend"})

XML configuration example: #

<context:component-scan base-package="com.yourproject.frontend, com.yourproject.backend" />

2. Verify Maven Module Dependencies #

Since your project is split into two modules, the frontend module must depend on the backend one. Open your frontend module's pom.xml and confirm this dependency exists:

<dependency>
    <groupId>your-project-group-id</groupId>
    <artifactId>backend-module-artifact-id</artifactId>
    <version>your-project-version</version>
</dependency>

After adding it, right-click the frontend project in Eclipse → Maven → Update Project to ensure dependencies are loaded correctly.

3. Check Autowiring Type Matching #

If you're using @Autowired in your Controller, make sure:

• There's no ambiguity: If multiple beans implement the same interface, use @Qualifier("beanName") to specify which one to inject, or mark one bean with @Primary
• The bean you're autowiring actually exists: Double-check class names, package paths, and that you didn't forget the Spring annotations (@Service/@Repository) on the backend class

4. Validate Hibernate-Related Bean Configurations #

For your backend Hibernate setup:

• Ensure your SessionFactory (or EntityManagerFactory if using JPA) is properly configured with a valid DataSource
• Confirm entity classes are being scanned (via setPackagesToScan in JavaConfig or <mapping> tags in XML)

Example JavaConfig for SessionFactory:

@Bean
public LocalSessionFactoryBean sessionFactory(DataSource dataSource) {
    LocalSessionFactoryBean sessionFactory = new LocalSessionFactoryBean();
    sessionFactory.setDataSource(dataSource);
    sessionFactory.setPackagesToScan("com.yourproject.backend.entity"); // Path to your Hibernate entities
    sessionFactory.setHibernateProperties(hibernateProperties());
    return sessionFactory;
}

5. Check the Full Error Stack Trace #

The short error message you provided only tells half the story. The full stack trace will show exactly which bean failed to create, and the root cause—whether it's a missing dependency, circular reference, or Hibernate configuration mistake. If you can get the full log, it'll speed up troubleshooting a lot.

6. Rule Out Spring Security Configuration Issues #

Since your Controller uses Spring Security classes, make sure your Security configuration isn't blocking bean creation:

• If your Service classes use method-level security annotations like @PreAuthorize, add @EnableGlobalMethodSecurity(prePostEnabled = true) to your Spring Security configuration class

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