Mysql driver issue with Deploytool 1.3

Question

Hi,
I would like to have J2EE 1.3 container managed entity beans being able to talk with a Mysql database . I have added my jar file to deploytool and have the mysql database server running and the database table ready to be used. I am using Mysql Connector Java 3.0 and have put the required driver jar file into the ext directory of the JAVA_HOME path. I have windows XP.
Here is my configuration in deploytool :
Tools--> Server configuration --> Data source --> standart
JDBC driver : com.mysql.jdbc.Driver
JNDI name : jdbc/zob
JDBC url : jdbc:mysql (the database is running on localhost and the table to use is ready)
Then in the entity tab of my bean --> Deployment Settings --> Database Settings, I put jdbc/zob as JNDI name. No username or password is required.
If I try to generate Default SQL, I get the following error:
Erroe: while generating SQL
java.rmi.ServerException:RemoteException occured in server thread;nested exception is:
java.rmi.RemoteException: Error connecting to database;nested exception is:
java.sql.SQLException:No suitable driver
Please make sure the database name/user/password is valid and the J2EE server and database are running.
I would be very grateful for help because I can't see what is missing or wrong. Thank you very much in advance.

Answer 1

First thing to do is try to narrow in on the problem a little bit. Try writing a simple test JSP or something that runs on the container to manually get a Connection from your Connection Pool. Then do a simple query to make sure you can actually connect.
InitialContext ic = new InitialContext();
DataSource ds = (DataSource) ic.lookup("java:comp/env/jdbc/zob");
Connection conn = ds.getConnection();
do your test query
...Once you have established that your Connection Pool is working, then go ahead and try to get your entity bean working. I haven't used MySQL before, I have always used Oracle on some remote server, never on localhost. Maybe the URL convention is different when it's on localhost, but it seems like you're missing the host, port, and instance parts; you just have the driver.
I'm sure you've already checked this but I'll say it just in case, make sure you have your driver class somewhere that the container can see it. I know, it's obvious, but you never know...
Good luck!!