Wylie, Kirk wrote:
- Putting the .jar files ANYwhere (in order of attempts, webapp's WEB-INF/lib, CATALINA_BASE/lib, CATALINA_HOME/lib) - Results in the following statement occurring in the logs: Cannot create JDBC driver of class 'oracle.jdbc.OracleDriver' for connect URL 'jdbc:oracle:thin@//fodevdbsx1.london:1521/fodev3.london'
Do you have a stack trace for this. Can you turn up the logging level and get one?
This indicates to me that the Oracle driver is being loaded, but it's being stopped from actually creating the instance for some reason.
Agreed.
The complication here is that Blojsom DOES NOT use, by default, JNDI resources. Rather, it sets up its own DBCP DataSource in its Spring+Hibernate configuration, which is what's failing here. This is NOT a <Resource> problem. Just to make sure, when I removed the DBCP implementation in blojsom, it failed, because it couldn't find the catalina copies.
If you are not using JNDI then you should be able to put the Oracle JARs in WEB-INF/lib. I'd also restore catalina.properties to the original to limit the changes.
Has anybody experienced anything like this in the past either with Blojsom or some other application which isn't using JNDI resources for database connections using Tomcat 6?
I have used DBCP directly in web-apps without a problem with 4, 5 and 6. Mark --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]