Spring3 problems-org. gjt. mm. mysql. Drivernotfound in fact, this problem is often quite simple. Generally, if the classpath does not contain the mysql driver package, no error will be reported after configuration. However, a strange problem was found during the use of spring3.1. The jar package is already in classpath, but after being started, org. gjt will be reported as long as it is called to the database.
Spring3-org. gjt. mm. mysql. Driver not found is actually a very simple problem. Generally, if the mysql Driver package is not found in classpath, no error will be reported when the configuration is complete. However, a strange problem was found during the use of spring3.1. The jar package is already in classpath, but after being started, org. gjt will be reported as long as it is called to the database.
Spring3-org. gjt. mm. mysql. Driver not found
In fact, this problem is often quite simple. Generally, if the classpath does not contain the mysql driver package, no error will be reported when the configuration is complete. However, a strange problem was found during the use of spring3.1. The jar package is already in classpath, but after being started, the org. gjt. mm. mysql. the Driver cannot be found. This problem has been plagued for many days. After Baidu put the mysql Driver package under the EXT extension directory of java, everything runs OK. Although the problem has been solved, it is still very troublesome to put the jar package under the JDK lib package every time during deployment. After subsequent analysis, the data source "org. apache. tomcat. dbcp. dbcp. basicDataSource "(in the commons-dbcp.jar) does not exist in the project. It is strange that why does spring not report an error after it starts the container? The single Singleton is loaded when the container is started. The reason should be that the class cannot be found.
Ah for the time being first put the "commons-dbcp.jar" in the path to use it, and then think about the reasons.
