RE: [WDSCI-L] AS400JDBCDRIVER Not Found

[Colin Williams <colin.williams@xxxxxxxxxxxx>]

Paul,

The other option is to add the jar to your EAR file as a utility jar, 
then to your project as a dependant jar,

then you don't need to add it to the servers classpath, or your projects
build path. 

Cheers
Colin.W


-----Original Message-----
From: Paul Nicolay [mailto:Paul.Nicolay@xxxxxxxxxx] 
Sent: 19 February 2004 15:36
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] AS400JDBCDRIVER Not Found


Hi Ed,

No problem, I experienced the same issue recently as well.

Guess deploying via WAR or EAR file doesn't contain the server config, so
nothing happens with it (you'll need to set the classpath on the server
yourself).

Kind regards,
Paul


>----- Oorspronkelijk bericht -----
>Van: Fasano, Ed [mailto:efasano@xxxxxxxxx]
>Verzonden: donderdag, februari 19, 2004 02:44 PM
>Aan: 'wdsci-l@xxxxxxxxxxxx'
>Onderwerp: [WDSCI-L] AS400JDBCDRIVER Not Found
>
>To all who are trying to help me with this:
>
>Paul, thank you, adding it to the server path worked.  I am running 
>this in the test environment.  What happens when it is moved over from 
>test, does it stay in the projects classpath or still on the server?
>
>Ed Fasano



_______________________________________________
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.