Spring Boot部署Tomcat 8.5遇‘dataSource必填’错误求助

Hey there, let's work through this frustrating error you're facing. That "Property 'dataSource' is required" message usually means your Spring Boot app can't find or properly wire up the JNDI data source you configured in Tomcat. Let's go through each part of your setup step by step to fix this.

1. Validate Tomcat's JNDI Configuration in context.xml #

First, double-check your context.xml Resource definition—small typos or missing properties here will break everything. Here's what a correct setup should look like (adjust for your database type):

<Resource name="jdbc/YourDBName"
          auth="Container"
          type="javax.sql.DataSource"
          driverClassName="com.mysql.cj.jdbc.Driver" <!-- Use your DB's driver -->
          url="jdbc:mysql://localhost:3306/your_database"
          username="db_username"
          password="db_password"
          maxTotal="100"
          maxIdle="20"
          maxWaitMillis="10000"/>

• Key checks:
  • The name value (e.g., jdbc/YourDBName) must match exactly what you reference in your Spring Boot code.
  • Make sure the database driver JAR (like mysql-connector-java) is placed in Tomcat's lib directory—not just your app's WEB-INF/lib. Tomcat manages the JNDI data source, so it needs direct access to the driver.

2. Fix Spring Boot's DataSource Bean & Disable Auto-Configuration #

Spring Boot loves to auto-configure things, which can clash with your JNDI setup. Here's how to fix it:

a. Disable Auto-Configuration for Data Sources #

Add exclude to your @SpringBootApplication annotation to prevent Spring from trying to create an embedded data source:

@SpringBootApplication(exclude = {DataSourceAutoConfiguration.class, HibernateJpaAutoConfiguration.class})
public class YourSpringBootApp {
    public static void main(String[] args) {
        SpringApplication.run(YourSpringBootApp.class, args);
    }
}

b. Correctly Look Up the JNDI Data Source #

Create a configuration class to fetch the JNDI data source properly:

@Configuration
public class DataSourceConfig {
    @Bean
    public DataSource dataSource() throws NamingException {
        InitialContext initialContext = new InitialContext();
        // Match the name from context.xml, prefixed with java:comp/env/
        return (DataSource) initialContext.lookup("java:comp/env/jdbc/YourDBName");
    }
}

Alternatively, you can use @Resource to inject it directly into components, but the configuration bean approach keeps things centralized.

3. Verify CartDao's DataSource Injection #

Make sure your CartDao is correctly receiving the DataSource via dependency injection—no manual lookup here! The constructor injection approach is the most reliable:

@Repository
public class CartDao {
    private final DataSource dataSource;

    // Constructor injection (Spring will auto-wire the DataSource bean we created)
    public CartDao(DataSource dataSource) {
        this.dataSource = dataSource;
    }

    // Your DAO methods here...
}

Avoid using @Value or manual JNDI lookups in the DAO itself—let Spring handle the wiring.

4. Check Your pom.xml Setup #

Since you're deploying to an external Tomcat, your Maven setup needs a few tweaks:

• Set packaging to war:

  <packaging>war</packaging>
  

• Exclude Spring Boot's embedded Tomcat dependency:

  <dependency>
      <groupId>org.springframework.boot</groupId>
      <artifactId>spring-boot-starter-web</artifactId>
      <exclusions>
          <exclusion>
              <groupId>org.springframework.boot</groupId>
              <artifactId>spring-boot-starter-tomcat</artifactId>
          </exclusion>
      </exclusions>
  </dependency>
  

• Add the Servlet API dependency with provided scope (Tomcat already provides this):

  <dependency>
      <groupId>javax.servlet</groupId>
      <artifactId>javax.servlet-api</artifactId>
      <version>3.1.0</version>
      <scope>provided</scope>
  </dependency>
  

5. Final Validation Steps #

• Restart Tomcat: Always restart after modifying context.xml—changes won't take effect otherwise.
• Check Logs: Look at Tomcat's catalina.log and localhost.log for errors related to JNDI initialization (e.g., driver not found, database connection failures). These logs will often give you more clues if the main error message is vague.
• Test the App: Deploy your war file again and see if the error clears up.

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