Hi, If you are correct I think the passage in the spec (8.1.1.2) is confusing. I would have thought putting the "." there deliberately makes you think only files with the .jar extension and not all J2EE module types.
Section 8.1.1 "A J2EE module is a collection of one or more J2EE components of the same component type (web, EJB, application client, or Connector) with one module deployment descriptor of that type." Further down in the same section it starts to refer to ".ear" files. If this by refering to .jar is meant to cover .jar and .war files it is badly worded. "The requirement here only applies to JAR format files containing class files or resources to be loaded directly by a standard ClassLoader; such files are always named with a .jar extension. It does not cover other JAR format files such as .ear files that are not typically loaded directly by a ClassLoader, but see the specifications for such files for details." The servlet v2.3 spec also states, "Web containers are !recommended! to have a mechanism by which web applications can learn what JAR files containing resources and code are available" I know you could argue that this is symantics and the intention is to cover all four enterprise JAR file types .jar, .rar, .jar and .ear. When I read this it is not the first thing that comes to my mind. David --- Tyler Jewell <[EMAIL PROTECTED]> wrote: > The J2EE spec in section 8.1.1.2 is referring to the > JAR file type, not > files that end in a .jar extension. WAR and EJB JAR > modules are both JAR > file types. > > -----Original Message----- > From: A mailing list for Enterprise JavaBeans > development > [mailto:[EMAIL PROTECTED]]On Behalf Of David > Jones > Sent: Wednesday, December 12, 2001 3:56 PM > To: [EMAIL PROTECTED] > Subject: Re: Class-Path references in WAR archive > manifest > > > Hi, > > Could you tell me where I could find it in the specs > that it is now mandatory for Containers to support > Class-Path references in WAR files. > > The Servlet 2.3 Spec (Section 9.7.1) recommends that > WAR files can use the extension mechanism but it is > not mandatory. > > The J2EE 1.3 spec (Section 8.1.1.2) just talks about > the .jar implementation. > > I appreciate BEA Weblogic supports this. > > David > > --- Tyler Jewell <[EMAIL PROTECTED]> wrote: > > The articles were written before the final version > > of J2EE 1.3 was > > completed. The final version of the spec now > > mandates that Manifest > > Class-Path: capability be for EJB JARs and WARs. > I > > liken the WEB-INF\lib > > directory to be a place to store all libraries > that > > should only be loaded by > > the web app classloader while the manifest > > Class-Path: libraries are loaded > > by the "EAR" classloader at a global level. > > > > And, for posterity, the articles came first and > the > > chapter came second ;-) > > > > Tyler Jewell > > Director, Technical Evangelism > > 978-884-5355 > > > > BEA eWorld 2002, THE 7th ANNUAL BEA CONFERENCE > > San Diego Convention Center > > San Diego, California > > February 24 - 27, 2002 > > www.bea.com/events/eworld/2002/ > > <http://www.bea.com/events/eworld/2002/> > > > > > > > > -----Original Message----- > > From: A mailing list for Enterprise JavaBeans > > development > > [mailto:[EMAIL PROTECTED]]On Behalf Of > Fred > > Loney > > Sent: Wednesday, December 12, 2001 2:28 PM > > To: [EMAIL PROTECTED] > > Subject: Re: Class-Path references in WAR archive > > manifest > > > > > > Perhaps more germane to the question is the > > follow-up article at > > > > > http://www.onjava.com/pub/a/onjava/2001/07/25/ejb.html > > > > which addresses class sharing among wars in an > ear. > > Both articles are > > drawn from the "Professional Java Server > Programming > > J2EE 1.3 Edition" > > chapter reproduced at > > > > > http://www.theserverside.com/resources/articles/J2EE-Deployment/chapter. > > html. > > > > The upshot is that if the app server is J2EE 1.3 > > compliant then a common > > support jar declared as a dependency in an EJB > > module Manifest classpath > > entry is available to all web apps in the ear. > > Nothing is said about war > > Manifest classpath entries. > > > > Fred Loney > > Spirited Software, Inc. > > www.spiritedsw.com > > > > ----- Original Message ----- > > From: "David Jones" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Wednesday, December 12, 2001 8:50 AM > > Subject: Re: Class-Path references in WAR archive > > manifest > > > > > > > Hi, > > > > > > Here is a good article about the subject > > > > > > > > > http://www.onjava.com/pub/a/onjava/2001/06/26/ejb.html > > > > > > It states that Application Servers do not have > to > > > support classpaths in the manifest file for WAR > or > > RAR > > > files. > > > > > > However I recently found an article in the BEA > > > documentation that says it does support it for > WAR > > > files, > > > > > > David > > > > > > --- "J. Matthew Pryor" > <[EMAIL PROTECTED]> > > > wrote: > > > > Lets say I have an .ear wherein I want to > > package 3 > > > > webapps > > > > > > > > All 3 webapp rely on the same jar file > > > > > > > > I know this works > > > > > > > > app/ > > > > webapp1/ > > > > META-INF/lib/needed.jar > > > > index.jsp > > > > webapp2/ > > > > META-INF/lib/needed.jar > > > > index.jsp > > > > webapp3/ > > > > META-INF/lib/needed.jar > > > > index.jsp > > > > > > > > My 'diagram' might be a bit confusing, since > the > > > > WARs in the EAR are > > > > archives, but I have shown them 'expanded', I > > hope > > > > it is clear enough. > > > > > > > > I was hoping that I could do this : > > > > > > > > app/ > > > > needed.jar > > > > webapp1/ > > > > META-INF/MANIFEST.MF > > > > index.jsp > > > > webapp2/ > > > > META-INF/MANIFEST.MF > > > > index.jsp > > > > webapp3/ > > > > META-INF/MANIFEST.MF > > > > index.jsp > > > > > > > > Where MANIFEST.MF would look like > > > > > > > > Manifest-Version: 1.0 > > > > Created-By: Ant 1.4 > > > > Class-Path: needed.jar > > > > > > > > It is not clear to me from reading the J2EE > 1.3 > > spec > > > > that manifest > > > > Class-Path entries in WARs are supported > > > > > > > > Perhaps I have to include a minimal jar in > each > > > > meta-inf/lib that would that > > > > have its own manifest that would reference > > > > needed.jar, something like > > > > > > > > Manifest-Version: 1.0 > > > > Created-By: Ant 1.4 > === message truncated === ===== David J. Jones, <[EMAIL PROTECTED]>, Virgin Mobile USA, 8th Floor, 22 Fourth Street, San Francisco, CA, 94103, Work: 415 932 5470. USA. Fax: 415 358 4999. __________________________________________________ Do You Yahoo!? Check out Yahoo! Shopping and Yahoo! Auctions for all of your unique holiday gifts! Buy at http://shopping.yahoo.com or bid at http://auctions.yahoo.com =========================================================================== 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".
