tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Briggs, Patrick" <pbri...@clinitech.net>
Subject RE: Tomcat -> MySQL = No suitable driver ERROR
Date Thu, 01 Jul 2004 16:35:39 GMT
Why does it have to be so difficult?  Pretty soon I'll have to give up and
go back to PHP.  What I really want to do is try out Javaserver Faces.

-----Original Message-----
From: Robert Harper [mailto:robert@iat-cti.com]
Sent: Thursday, July 01, 2004 9:38 AM
To: 'Tomcat Users List'
Subject: RE: Tomcat -> MySQL = No suitable driver ERROR


I have seen this one too many times. It usually has to do with the naming
lookup. I have had to keep "playing" with the form of the name until it
worked.

Robert S. Harper
801.265.8800 ex. 255

> -----Original Message-----
> From: Briggs, Patrick [mailto:pbriggs@clinitech.net]
> Sent: Thursday, July 01, 2004 10:20 AM
> To: 'Tomcat Users List'
> Subject: RE: Tomcat -> MySQL = No suitable driver ERROR
> 
> Yeah, I just tried that and still no go.  Still getting:
> 
> javax.servlet.ServletException: Unable to get connection, DataSource
> invalid: "org.apache.commons.dbcp.SQLNestedException: Cannot create JDBC
> driver of class '' for connect URL 'null', cause: No suitable driver"
> 
> -----Original Message-----
> From: Jan Behrens [mailto:jan@diekleinedomain.de]
> Sent: Thursday, July 01, 2004 1:04 AM
> To: 'Tomcat Users List'
> Subject: RE: Tomcat -> MySQL = No suitable driver ERROR
> 
> 
> David is right,
> 
> you will need to rename {Catalina_Home}/webapps/DBTest/WEB-INF/DBTest.xml
to
> {Catalina_Home}/webapps/DBTest/WEB-INF/web.xml and hopefully all will be
up
> and running.
> 
> Jan
> 
> -----Original Message-----
[snip]



---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org

This e-mail message, including any attachments, is for the sole use of the
intended recipient(s) and may contain confidential or privileged
information.  Any unauthorized review, use, disclosure or distribution is
prohibited.  If you are not the intended recipient, please contact the
sender by reply e-mail and destroy the message.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message