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
