Steve Kirk wrote:
When TC starts up, the webapp deploys OK from its war file, and the
context.xml is copied to the /conf/[engine]/[host]/ folder OK, without any
parsing errors logged. The connection pool initially seems to work, in the
sense that this code executes OK: Context ctx = new InitialContext();
String resourceString = "java:comp/env/jdbc/" +
config.getString(ConfigConstants.JNDI_DATABASE_RESOURCE_NAME);
DataSource pool = (DataSource)ctx.lookup(resourceString);
However, an Exception is thrown the first time that I do this: Connection conn = pool.getConnection();
This doens't mean much. You will get a DBCP object event if connection data is wrong. It will however fail on attempting to obtain a connection. In my oppinion it would be nice if it failed during web app deployment, thus not leading us to believe all is OK. Although it would be yet another source of frustration. And I can see an argument that failing to correctly setup a DataSource should not invalidate the entire web app, since it could be setup with N DataSources and inteligence to choose one that works.
-----------------------------------------------------------------
Exception caught when establishing/testing database pool****
cause[0]: org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create JDBC
driver of class '' for connect URL 'null'
This most commonly means that the definition of the DataSource resource lacks driver definition. Could it be that you've missed the fact that DataSource JNDI resource setup definition has changed in TC 5.5? It is no longer with those <parameter><name>...</name><value>...</value></parameter>. Check it out.
Nix.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
