Christopher Schultz wrote: > Mark, > > On 9/4/2009 11:21 AM, Mark Thomas wrote: >> Christopher Schultz wrote: >>> Jamez, >>> >>> On 9/3/2009 11:15 PM, jamez smith wrote: >>>> This is the exception when removing the <context> element from the >>>> server.xml: >>>> [ERROR] [Cannot create JDBC driver of class '' for connect URL >>>> 'null']org.apache.commons.dbcp.SQLNestedException: Cannot create JDBC >>>> driver >>>> of class '' for connect URL 'null', cause: >>>> java.sql.SQLException: No suitable driver >>>> at java.sql.DriverManager.getDriver(DriverManager.java:243) >>>> at >>>> org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:743) >>>> at >>>> org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:518) >>> Okay, now we're back to a simpler problem. I don't believe Tomcat 4.1.x >>> uses META-INF/context.xml files, which is a shame, because you can't >>> define context-specific <Resource> elements anywhere. It looks like >>> you're going to have to have your <Context> in server.xml no matter what. >> Huh? > >> You put myapp.xml in the webapps directory in Tomcat 4.1.x. > > Sorry, it's been a while since I used Tomcat 4.1, but I was suggesting > that he disable autoDeply, in which case using an XML file in webapps > wouldn't help.
Sorry missed that. In that case the Context element would have to be in server.xml but you could still have a context specific resource defined in that Context element. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
