You should be able to package them exactly according to the J2EE 1.3. spec. Sorry for mis-leading you in my previous post. WAS 4 is J2EE 1.2, but implements some 1.3 features, regarding dependent jars.
Your archive structure seem to be fine. Make sure you have the following entry in your MANIFEST.MF files of the ejb-jar and the war: Class-Path: a.jar another.jar etc.jar /Johan Den 2003-02-03 15.54, skrev "Ashwani Kalra" <[EMAIL PROTECTED]>: > > hi john, > > I have one ear file which contains ejb jar and war file. jsps in the war > access some common files(a.jar) and ejb also access the common files(a.jar) > in addition to third party jars like log4.jar. How to package in best way > so WAS takes them. > > Regds > Ashwani > > > > > > Johan Eltes > <johan.eltes@CALL To: [EMAIL PROTECTED] > ISTA.SE> cc: (bcc: > ashwani.kalra/Polaris) > Sent by: A Subject: Re: WAS not picking up > jars from web-inf\lib dir > mailing list for > Enterprise > JavaBeans > development > <EJB-INTEREST@JAV > A.SUN.COM> > > > 02/03/2003 05:19 > PM > Please respond to > Johan Eltes > > > > > > > > My experience from WAS is that its classloadeer implementation is more > spec complient than most other J2EE 1.2 implementations. It is > important that you do not list module-jars in th modules Classpath- > entry of the modules manifest file. > > Just for my understanding: > > - The ear conatins a war > - The war has a jar in its lib directory > - Classes of the wars "classes" directory can not load classes of the > jar of the lib directory of the same war > - There is no entry in the Classpath-field of teh wars manifest, > referensing the jar on the wars lib directory. > > This set-up usualy works well. > > /Johan > > citerar Ashwani Kalra <[EMAIL PROTECTED]>: > >> >> Hi Sameer, >> I will go through the article. But any server that complies with > j2ee must >> pickup the clasess from web-inf\classes and web-inf\lib dir. Does WAS >> deviates from this, ? >> >> Regds >> Ashwani >> >> >> >> Sameer Bhardwaj >> <[EMAIL PROTECTED] To: >> [EMAIL PROTECTED] >> HSPAN.COM> cc: (bcc: >> ashwani.kalra/Polaris) >> Sent by: A mailing list Subject: > Re: WAS >> not picking up jars from web-inf\lib dir >> for Enterprise JavaBeans >> development >> <[EMAIL PROTECTED] >>> >> >> >> 02/03/2003 10:25 AM >> Please respond to Sameer >> Bhardwaj >> >> >> >> >> >> >> >> Hi Ashwani, >> This is because of websphere class loading sequence. refer this for > more >> info >> >> > http://www7b.software.ibm.com/wsdd/library/techarticles/0112_deboer/debo > er.h >> >> tml >> >> regards >> >> sameer >> >> >> >> -----Original Message----- >> From: Ashwani Kalra [mailto:[EMAIL PROTECTED]] >> Sent: Monday, February 03, 2003 10:19 AM >> To: [EMAIL PROTECTED] >> Subject: WAS not picking up jars from web-inf\lib dir >> >> >> hi, >> >> Little bit off topic. but related to j2ee. >> I am making ear file and trying to deploy it on was 4.01. We are > having >> some common utility classes and third party jars in web-inf\lib dir. >> WAS is not picking up these classes and when we put the jars in WAS > lib >> dir, it picks it up. >> Has any body faced such problem? >> >> Regds >> Ashwani >> >> > ======================================================================== > === >> To unsubscribe, send email to [EMAIL PROTECTED] and include in > the body >> of the message "signoff EJB-INTEREST". For general help, send email > to >> [EMAIL PROTECTED] and include in the body of the message "help". >> >> >> >> >> >> > > =========================================================================== > To unsubscribe, send email to [EMAIL PROTECTED] and include in the body > of the message "signoff EJB-INTEREST". For general help, send email to > [EMAIL PROTECTED] and include in the body of the message "help". > > > > > > =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
