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
> > Class-Path: ......
> eeded.jar
> >
> >
> > Anyone care to comment/clarify ?
> >
> > Thanks,
> > Matthew
> >
> >
>
========================================================================
===
> > 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".
> >
>
>
> =====
> 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".
>

===========================================================================
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".

Reply via email to