RE: [WDSCI-L] Connecting to Oracle in WDSCi

[Colin Williams <colin.williams@xxxxxxxxxxxx>]

Paul, 

Im not sure whats causing your problem, but another alternative is to put
the jar file under the EAR project. Then click on properties on your web
project and select it as a JAR Dependency under Java JAR Dependencies. 

This method also automagically adds it to your build path.

Cheers
Colin.W

-----Original Message-----
From: Paul Nicolay [mailto:Paul.Nicolay@xxxxxxxxxx] 
Sent: 12 February 2004 15:32
To: Websphere Development Studio Client for iSeries
Subject: [WDSCI-L] Connecting to Oracle in WDSCi


Hi,

I have a Java application which is developed in WDSC, and runs fine within
Tomcat on iSeries, but when trying to run it in WDSC with a WAS server, I
always get 

[12/02/04 16:26:49:764 CET]  a443d17 SystemErr     R
java.lang.ClassNotFoundException: oracle.jdbc.driver.OracleDriver

I have my classes12.zip in the project Build Path, as well as in the servers
classpath, but all to no avail ?

Where should I put it... what is going wrong ?

Thanks,
Paul


_______________________________________________
This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.
This e-mail has been sent by a company of Bertram Group Ltd, whose registered 
office is The Nest, Rosary Road Norwich NR1 1TF. 
This message, and any attachments, are intended solely for the addressee and 
may contain privileged or confidential information.  If you are not the 
intended recipient, any disclosure, copying, distribution or any action taken 
or omitted to be taken in reliance on it, is prohibited and may be unlawful.  
If you believe that you have received this email in error, please contact the 
sender immediately. Opinions, conclusions and statements of intent in this 
e-mail are those of the sender and will not bind a Bertram Group Ltd company 
unless confirmed in writing by a director independently of this message. 
Although we have taken steps to ensure that this email and any attachments are 
free from any virus, we advise that in keeping with good computing practice the 
recipient should ensure they are actually virus free.