>> 1. Have one of your JSPs dump out the value of the jdbc.drivers system
>> property to ensure its being set
> I didn't understand the first step you mention, Could you
> please explain me it in other words?
Add a JSP like this to your webapp:
<html><body><% out.println(System.getProperty("jdbc.drivers")) %></body></html>
(or add a similiar line to one of the existing JSPs) to check that the jdbc.drivers
property is actually being set, and set to the value you intend. I find the tomcat
startup scripts a little confusing. This is just a sanity check to demonstrate that
the property is actually being set the way you intend.
>> 2. Have one of your JSPs try to access one of the DBCP classes directly, to
>> ensure the classpath is correct (e.g., invoke
>> Class.forName("org.apache.commons.dbcp.PoolingDriver"))
By this I mean add a JSP like this to your webapp:
<html><body><% out.println(Class.forName("org.apache.commons.dbcp.PoolingDriver"))
%></body></html>
While you're at it, you could try to ensure that your .jocl file is visible to your
webapp also:
<html><body><% PoolingDriver.class.getResource("mypool.jocl") %></body></html>
In other words, I guess I'm saying that in my experience a "no suitable driver"
exception points to classpath issues, and the classpath/classloader issues are
complicated by servlet containers (since there's at least two classloaders to be
concerned with--Tomcat's and the webapp's).
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
