Re: [WDSCI-L] Newbie Question Number One

["Mark Phippard" <MarkP@xxxxxxxxxxxxxxx>]

Joe,

Instead of linking those external JAR files to your project by setting the 
Java Build Path properties on the project, you have to physically copy 
them to the /WEB-INF/lib folder of your web application.  This will cause 
them to automatically be in both your build path as well as your runtime 
classpath.  And, of course, since they are now physically a part of your 
project they will also be exported to your ear file.

Mark






"Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
05/28/2003 03:34 PM
Please respond to Websphere Development Studio Client for iSeries 
 
        To:     "Websphere Development Studio Client for iSeries" 
<wdsci-l@xxxxxxxxxxxx>
        cc: 
        Subject:        [WDSCI-L] Newbie Question Number One


Okay, I'm trying, really I am, to work with the new J2EE Deployment Model.
I will try to keep my negative comments to myself, and simply ask real 
world
questions.

I have a J2EE project in WDSC.  It's got a single EAR and a single WAR.
There's also a secondary project which contains my common runtime 
packages.

I did two things - I added the seconday project as an external jar, and 
then
added a couple of "real" external jar files from my C: drive (I have a
folder, C:\Java\lib, specifically designated just for that purpose). Well,
this worked swimmingly!  I can fire up the project in the WAS5X test
environment, and even launch my servlet and see good things happen.

So now it's time to deploy.  Like a good boy, I export my project to an 
EAR
file.  And just for the fun of it, I looked inside the EAR and saw a WAR,
and in the WAR was not only the stuff from the J2EE project, but also the
entire secondary project had been included as a single JAR.

I install the EAR file on WAS5X on the host, fire it up and WHAM!  I can 
rnu
my servlets!  WAY COOL, FOLKS!  Phil, your team has done an excellent job
here.

However, I didn't see the external jar files.  In fact, the only thing I 
see
is a .classpath in my WAR folder that still has the links to 
"C:\Java\lib",
which clearly won't work.  And any servlets accessing those external JARs
fails.  And in fact, it seems to dump the server and restart it.  This is
the "not way cool" part of the program.

I had hoped that the EAR packager would pick up those external JARs and
stuff them in the lib folder for the WAR.  Since this didn't happen, I 
guess
I don't know what the steps are to handle an external jar.

Joe

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