RE: [WDSCI-L] Newbie Question Number One

["Mark Phippard" <MarkP@xxxxxxxxxxxxxxx>]

The EAR file does have an area where you can put "shared code" so that it 
does not have to reside under each web application.  You can package your 
EAR file this way by using IBM's Application Assembly Tool (AAT).  As far 
as I know, the WSAD tooling does not provide access to these sort of 
advanced EAR file features.  I could definitely be wrong though.  If it 
does, it seems like it would have to be done through the EAR project 
somewhere.

All that aside, if you are using any kind of version control, even CVS, it 
is very easy to manage this (at least for JAR's like JTOpen, Struts, 
Xerces etc. where they change slowly).  You just connect to the repository 
and add your project and everything comes in all configured.  If you have 
some internal projects you want to package it sounds like you have already 
discovered that you can define the Java Project in which you develop that 
code as a "Library Project" to your Web Project and its code is then 
automagically kept updated in the Web Project.

Mark









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


> From: Mark Phippard
>
> 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.

Okay, so if I have many applications, and they use the same external JARs, 
I
have to copy those JARs to every /WEB-INF/lib folder of every application.

And on the PC side, that means that every developer has to make sure that
they have the appropriate JAR files in their /WEB-INB/lib folder for every
application.  And while I assume some of the more aggressive change
management tools handle this, the manual effort involved to keep all these
environments in sync could be rather large, couldn't it?

It would be so much easier to simply have everybody point to a shared 
drive
where the common JAR files reside, and pick those up when generating an 
EAR
file.

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.