This week's giveaway is in the EJB and other Java EE Technologies forum. We're giving away four copies of EJB 3 in Action and have Debu Panda, Reza Rahman, Ryan Cuprak, and Michael Remijan on-line! See this thread for details.
I've worked with weblogic too. I get mySQL to work okay from applications. I work a jar file into my classpath and do the forName thing. It seems the reference implementation from Sun uses your classpath (sometimes). But I suspect that somewhre I need to tell it how to do the Class.forName stuff.
I've moved a little further forward. I've included the following in the config/default.properties file: jdbc.drivers=COM.cloudscape.core.RmiJdbcDriver rg.gjt.mm.mysql.Driver jdbc.datasources=jdbc/Cloudscape|jdbc:cloudscape:rmi:CloudscapeDB;create=true|jdbc/DataSource|jdbc:mysql://localhost/soup (soup is the name of my database in mySQL) All the JNDI stuff in the deploytool is set to jdbc/DataSource Here is where my problem is (with debug lines):
And here is what I see on the j2ee console: xxx 2.1 xxx 2.2 xxx 2.3 xxx 2.4 xxx 2.5 Cannot find principal mapping information for data source with JNDI name jdbc/DataSource xxx 2.6