Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@www.apache.org Received: (qmail 25293 invoked from network); 17 Aug 2004 16:15:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 17 Aug 2004 16:15:31 -0000 Received: (qmail 66687 invoked by uid 500); 17 Aug 2004 16:15:02 -0000 Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org Received: (qmail 66497 invoked by uid 500); 17 Aug 2004 16:15:01 -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 66483 invoked by uid 99); 17 Aug 2004 16:15:01 -0000 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=DNS_FROM_RFC_ABUSE,HTML_60_70,HTML_MESSAGE X-Spam-Check-By: apache.org Received: from [170.35.241.231] (HELO cingular.com) (170.35.241.231) by apache.org (qpsmtpd/0.27.1) with ESMTP; Tue, 17 Aug 2004 09:14:57 -0700 Received: from ([10.85.28.73]) by extmail02.cingular.com with ESMTP ; Tue, 17 Aug 2004 12:14:04 -0400 (EDT) Received: by s30004d004252.wdc.cingular.net with Internet Mail Service (5.5.2657.72) id ; Tue, 17 Aug 2004 12:14:04 -0400 Message-ID: <3165F742BA5A8E4194D3E014C17FB2100FAC2AB2@s30342g004006.wdc.cingular.net> To: 'Tomcat Users List' Subject: RE: JNDI Problem Date: Tue, 17 Aug 2004 12:14:01 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C48475.3583D9D0" From: "Graff, David" X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N ------_=_NextPart_001_01C48475.3583D9D0 Content-Type: text/plain; charset="iso-8859-1" Temporarily remove the res-ref entry from your web.xml file, and through the admin console add a resource link to the global resource in the context of your web app. Or add manually a resource link entry in your server.xml to the context entry. This is an annoying little quirk. -----Original Message----- From: Bussie, Andre D [mailto:andre.d.bussie@lmco.com] Sent: Tuesday, August 17, 2004 11:49 AM To: tomcat-user@jakarta.apache.org Subject: JNDI Problem Trying to set access datasource via JNDI. Using Tomcat 5.0.19 however I get the following error message Cannot create JDBC driver of class '' for connect URL 'null', cause: null Here is my server.xml file snippet maxWait 5000 maxActive 4 password url jdbc:hsqldb.hsql://localhost driverClassName org.hsqldb.jdbcDriver maxIdle 2 username sa Here is web.xml snippet Resource reference to a HSQLDB datasource instance that is configured in the server.xml file. hsqldb javax.sql.DataSource Container JSP code to access Context initContext = new InitialContext(); Context envContext = (Context)initContext.lookup("java:/comp/env"); DataSource ds = (DataSource)envContext.lookup("hsqldb"); Connection conn = ds.getConnection(); I followed the instructions from the tomcat web page what is causing this and how can I get this resolved to access the datasource through JNDI. Anyone ......... ------_=_NextPart_001_01C48475.3583D9D0--