Spring MVC XML配置中Autowired对象为空，通过Environment读配置遇问题

Got it, let's work through why your Environment is coming up null and how to fix the @Autowired problems in both your Java config and Spring MVC XML setups.

Java Config: Fixing Null Environment in AuthServiceImpl #

1. Double-Check Component Scan Coverage #

Your AppConfig uses @ComponentScan(basePackages = "com.asn.myutilities") — make sure your AuthServiceImpl class lives inside this package (or one of its sub-packages). If it's outside, Spring won't detect it as a managed bean, and @Autowired won't do anything at all.

2. Confirm AppConfig is Loaded by Spring #

Spring can't apply your config if it doesn't know about it. Depending on how you're starting your app:

• For annotation-based contexts, initialize it like this:

  AnnotationConfigApplicationContext context = new AnnotationConfigApplicationContext(AppConfig.class);
  

• If mixing with XML, add this to your XML file to pull in the config class:

  <bean class="com.asn.myutilities.AppConfig"/>
  <context:annotation-config/>
  

3. Don’t Use Environment Before Bean Initialization #

If you’re calling readValues() too early (like in the class constructor), Spring hasn’t finished injecting the Environment yet. Use @PostConstruct to run logic after the bean is fully set up:

@Service("authService")
public class AuthServiceImpl implements AuthService {
    @Autowired
    private Environment environment;

    // Runs right after the bean is fully initialized
    @PostConstruct
    public void initValues() {
        String myProperty = environment.getProperty("your.property.key");
        // Safe to use the value here
    }

    @Override
    public void readValues() {
        if (environment != null) {
            String value = environment.getProperty("your.property.key");
            // Your business logic here
        }
    }
}

Spring MVC XML Setup: Fixing @Autowired Nulls #

1. Enable Annotation Processing #

Add these lines to your XML config to let Spring handle annotations like @Autowired and @Service:

<context:annotation-config/>
<mvc:annotation-driven/>

2. Configure Component Scanning #

Make sure Spring finds and registers your service beans:

<context:component-scan base-package="com.asn.myutilities"/>

3. Set Up Property Loading for Environment #

To inject Environment in XML, register the property configurer bean:

<bean class="org.springframework.context.support.PropertySourcesPlaceholderConfigurer">
    <property name="locations">
        <list>
            <value>classpath:application.properties</value>
        </list>
    </property>
</bean>

4. Never Instantiate Beans Manually #

If you’re creating AuthServiceImpl with new AuthServiceImpl(), it’s not a Spring-managed bean — so @Autowired fields will stay null. Always get beans from the Spring context:

// Correct way
AuthService authService = context.getBean("authService", AuthService.class);
// Or inject it into another Spring-managed bean with @Autowired

5. Check Context Hierarchy #

Spring MVC has two contexts: the root context (loaded by ContextLoaderListener) and the servlet context (loaded by DispatcherServlet). Keep your service beans in the root context and controllers in the servlet context (which can access root context beans) to avoid cross-context injection issues.

Quick Debugging Tips #

• Check Spring’s startup logs for messages about AuthServiceImpl being initialized — this confirms it’s a managed bean.
• Print all bean names in the context to verify:

  String[] beanNames = context.getBeanDefinitionNames();
  for (String name : beanNames) {
      System.out.println(name);
  }
  

• Rule out circular dependencies (though this is unlikely with Environment injection).

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