After learning about EJB technology, I felt a little impressed. I decided to practice entitbean + sessionbean because entitbean (which is responsible for database operations on the server ), therefore, we need to configure the connection pool before this, the Weblogic I use, the problem mentioned in the title of the configuration, JDBC driver is not on the classpath, at first glance, I probably knew it was a problem with the driver jar package. Then, I put the package directly under the comm/lib directory of webliogc and re-connected the package. I still reported the exception, I decided to check it online. That is to say, we need to set classpath on the server first. Most of them are in commm/bin/commenv. CMD adds a sentence to this file:
Add: Set classpath = your driver jar path
OK. Now, restart the server. The connection prompt is "connection successful ".
Note: Although Weblogic and your selection help you automatically write the driver name, sometimes you need to write according to your driver:
Driver name and URL. Otherwise, your driver package may not match the driver name or URL provided by the driver package, and some errors are reported.