J2EE 1.3, section 8.1.1.2 A .jar file can reference another .jar file by naming the referenced .jar file in a Class-Path header in the referencing .jar file's Manifest file. The referenced .jar file is named using a URL relative to the URL of the referencing .jar file. The Manifest file is named META-INF/MANIFEST.MF in the .jar file. The Class- Path entry in the Manifest file is of the form Class-Path: list-of-jar-files-separated-by-spaces The J2EE deployment tools must process all such referenced files when processing a J2EE module that is or contains a .jar file. Any deployment descriptors in referenced .jar files are ignored when processing the referencing .jar file. The deployment tool must install the .jar files in a way that preserves the relative references between .jar files. Typically this is done by installing the .jar files into a directory hierarchy that matches the original application directory hierarchy. All referenced .jar files must appear in the logical class path of the referencing .jar files at runtime.
> -----Original Message----- > From: David Jencks [mailto:[EMAIL PROTECTED] > Sent: Thursday, March 13, 2003 11:31 AM > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-user] 3.0.4 -> 3.0.7 deployment > dependencies change? > > > does anyone know what the spec says to do with these linked > dependencies? > Is deploying a plain jar supposed to look at manifest cp > entries and follow > them? My understanding is the old behavior was not spec > compliant in that > if you referenced an ejb-jar in the manifest classpath it would be > deployed as an ejb-jar, not just deploying the classes. > > david jencks > > On 2003.03.12 21:59 Brian Wallis wrote: > > On Thu, 13 Mar 2003 10:32, Brian Wallis wrote: > > > I was building on 3.0.4 and have changed to 3.0.7. > > > > > > To resolve dependencies between jars I had Class-Path > entries in the > > > Manifests of the jars like so... > > > > > > in JavaCommon.jar META-INF/MANIFEST.MF there is an entry: > > > > > > Class-Path: Cis.jar > > > > > > which with 3.0.4 caused Cis.jar to be deployed before the > deployment of > > > JavaCommon.jar was completed thus making the classes in Cis.jar > > available > > > during the deployment of JavaCommon.jar. > > > > > > This no longer seems to work with 3.0.7. > > > > > > This did seem to be a reasonable way to define > dependencies between jar > > > files, is this not a good way to do it? Is there a better > way or is > > 3.0.7 > > > broken? > > > > OK, I see the change in MainDeployer.java at version > 1.28.2.23 (24th Dec) > > > > where the code to deploy a jar is changed to just add it to > the root > > DeploymentInfo class loader rather than deploy it. > > > > Unfortunately this means that if there are Class-Path entries in the > > manifest > > of these jar files it will be ignored so you cannot cascade the > > dependencies. > > > > If an EJB jar needs (simple) jars A.jar, B.jar and C.jar > then they all > > have to > > be listed in it's Class-Path rather than just listing C.jar > and having > > C.jar > > reference B.jar in it's Class-Path manifest entry and then > having B.jar > > reference A.jar in it's manifest. (which used to work prior > to 3.0.5). > > > > Am I assuming behaviour of the Class-Path manifest entry that is not > > intended? > > Should this work in the cascaded manner? > > > > brian wallis... > > > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by:Crypto Challenge is now open! > > Get cracking and register here for some mind boggling fun and > > the chance of winning an Apple iPod: > > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en > > _______________________________________________ > > JBoss-user mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-user > > > > > > > ------------------------------------------------------- > This SF.net email is sponsored by:Crypto Challenge is now open! > Get cracking and register here for some mind boggling fun and > the chance of winning an Apple iPod: > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > ------------------------------------------------------- This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
