No joy. The driver name I had is actually as documented, and works in a separate configuration used by the application. (Should also have mentioned that the Oracle version is 9.2.0.1). And it's definitely not that it can't find the driver JAR, since it throws a different error if I remove it from the Tomcat common/lib directory. NPE means it's expecting something to be instantiated that isn't, but the previous two issues are the only thing I can think of that I have control over and could conceivably cause that. I'm using the XML-based realm in as a stopgap in the meantime, but it sure would be nice to get this going.
-----Original Message----- From: Niaz Habib [mailto:[EMAIL PROTECTED] Sent: Sunday, July 04, 2004 10:39 PM To: Tomcat Users List Subject: Re: NullPointerException JDBCRealm Oracle Thin The last time I used Oracle JDBC Driver (classes12.zip), the JDBC Driver class was oracle.jdbc.driver.OracleDriver. I see that you are using oracle.jdbc.OracleDriver as driver class while defining JDBCDataSourceRealm. Try oracle.jdbc.driver.OracleDriver instead. Niaz --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
