Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 78539 invoked from network); 7 Jan 2003 12:14:44 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 7 Jan 2003 12:14:44 -0000 Received: (qmail 16172 invoked by uid 97); 7 Jan 2003 12:15:08 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org Received: (qmail 16099 invoked by uid 97); 7 Jan 2003 12:15:07 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 16010 invoked by uid 98); 7 Jan 2003 12:15:05 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <01d201c2b647$293eccf0$0b7bfea9@w9b1jqmyjsd9ds1> From: "David Hemingway" To: "Tomcat Users List" Subject: A solution: java.sql.SQLException: Cannot load JDBC driver class 'null' Date: Tue, 7 Jan 2003 23:20:26 +1100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_01CF_01C2B6A3.5C2BE420" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-OriginalArrivalTime: 07 Jan 2003 12:13:37.0672 (UTC) FILETIME=[35397880:01C2B646] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N ------=_NextPart_000_01CF_01C2B6A3.5C2BE420 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi all, I have found a solution to this problem. Its by no means elegant but if = you get as desperate as I have got then you may wish to do the same. It appears that none of the information that you specify in your = server.xml gets through to the actual dbcp stuff, don't ask me why. So = what I did was crack open the source and hardcode all the details into = org.apache.commons.dbcp.BasicDataSource. Then I rebuilt, redeployed and = everything works perfectly. I know this is not scalable or pretty but it = is a solution that *will* work. The only question I have left remaining = is that is it a security issue having the DB password wrapped up in that = jar? (I can't see one) assuming that the server is never compromised. = Thanks everybody for all the help given over the past couple of days, it = was very much appreciated. regards, Dave ------=_NextPart_000_01CF_01C2B6A3.5C2BE420--