|
Joe, I might be missing something here, but if you don't want to include the jars in the ear, then its ok, it just means you are ready, willing and able to handle getting those jars into the production server, which it sounds like you are. In the ear, gets published. Out of ear, not published. So, to do this, just set your project's build path to put directly to the jar files where they live on your disk, as did before I think. Then, to get Run On Server to work, you have to set the ws.ext.dirs classpath, which can be set for each server via the Path tab in the server configuration editor. That'll handle compiling in the IDE, and running in the IDE. For running on the server you deploy to, you'll just have to set this ws.ext.dirs classpath yourself. Phil Coulthard, STSM, iSeries AD, IBM Canada Ltd. coulthar@xxxxxxxxxxx 905-413-4076, t/l 969-4076 ----- Forwarded by Phil Coulthard/Toronto/IBM on 05/29/2003 09:51 PM ----- "Joe Pluta" <joepluta@xxxxxxx To: "Websphere Development Studio Client for iSeries" <wdsci-l@xxxxxxxxxxxx> others.com> cc: Sent by: Subject: RE: [WDSCI-L] Newbie Question Number One wdsci-l-bounces@x idrange.com > From: Joe Pluta > > It would also be nice to flag them as being added to the > classpath WITHOUT being exported, although I don't know if the > EAR/WAR model allows this. Why is this important? Well, in my particular case, my EAR file jumped from 350KB to 3.7MB because of included JAR files, and it's only including two JAR files. If you need a separate copy of several MB of JAR files for every application, and you have dozens or even hundreds of applications, then you can conceivably be talking gigabytes of wasted disk space. It might not matter so much on a PC, but it's pretty expensive on an iSeries. Joe
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.