Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <20840073.post@talk.nabble.com>
Date: Thu, 4 Dec 2008 10:57:50 -0800 (PST)
From: teamderby <mikehmurray@gmail.com>
To: derby-user@db.apache.org
Subject: Re: Tomcat derby JSP "java.sql.SQLException: No suitable driver"
In-Reply-To: <493422BD.2030804@frogthinker.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <738B94ED-B6DC-40F8-8754-2D4EC77A3724@gmail.com>
 <493422BD.2030804@frogthinker.org>


Emmanuel,

Thanks for your reply. I have tried using derby.jar instead of
derbyclient.jar and the result is exactly the same. Is there any more advice
you can give me?

Thanks,

Mike


Emmanuel Cecchet-5 wrote:
> 
> Michael,
> 
> You should have derby.jar in the classpath if you want to use embedded 
> mode.
>> CLASSPATH=\
>> Applications/apache-tomcat-6.0.18/lib/derbyclient.jar:\
> derbyclient.jar contains only the JDBC driver code 
> (http://db.apache.org/derby/docs/dev/adminguide/tadminappschangingyourclasspath.html)
>> <%
>> String driver = "org.apache.derby.jdbc.EmbeddedDriver";
> 
> Hope this helps,
> Emmanuel
> 
> -- 
> Emmanuel Cecchet
> FTO @ Frog Thinker 
> Open Source Development & Consulting
> --
> Web: http://www.frogthinker.org
> email: manu@frogthinker.org
> Skype: emmanuel_cecchet
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Tomcat-derby-JSP-%22java.sql.SQLException%3A-No-suitable-driver%22-tp20776666p20840073.html
Sent from the Apache Derby Users mailing list archive at Nabble.com.