Home/ Questions/Q 7866469
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-03T00:24:40+00:00

The javadoc says to load the my.sql.Driver class, the META-INF/services/java.sql.Driver file would contain the

  • 0

The javadoc says “to load the my.sql.Driver class, the META-INF/services/java.sql.Driver file would contain the entry: my.sql.Driver”.

Don’t webapps typically have a META-INF folder as a sibling of WEB-INF? However, JPA specs are looking for persistence.xml in WEB-INF/classes/META-INF/.

Which place is correct for services/java.sql.Driver?

By the way, I am getting “No suitable Driver” exception with it in both locations.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You should not provide it yourself. The JDBC driver JAR file should already contain it. At least, if it’s a JDBC 4.0 compliant driver. This is also explicitly mentioned in javadoc of DriverManager:

    The DriverManager methods getConnection and getDrivers have been enhanced to support the Java Standard Edition Service Provider mechanism. JDBC 4.0 Drivers must include the file META-INF/services/java.sql.Driver. This file contains the name of the JDBC drivers implementation of java.sql.Driver. For example, to load the my.sql.Driver class, the META-INF/services/java.sql.Driver file would contain the entry:

    my.sql.Driver

    Applications no longer need to explictly load JDBC drivers using Class.forName(). Existing programs which currently load JDBC drivers using Class.forName() will continue to work without modification.

    If yours doesn’t have, then it’s apparently not a JDBC 4.0 compliant driver. You’d need to explicitly load the driver yourself, or to upgrade to a JDBC 4.0 compliant driver, or just use a container managed DataSource (which offers more advantages as well, such as connection pooling).

    • 0