So, let me follow up and verify some myths/facts: 1. Jboss 2.4.4 successfully deployed our EAR file, with about 4 EJBs using the same methodology of using a manifest's Class-Path: entry 2. Jboss 3.0.0 beta has had its deployment strategy changed, and our EAR deployment now breaks due to undetermined deployment of the included jars 3. JB 3 cannot predictably deploy jars found in the ear and defined in a bean's manifest Class-Path, even though this is essential to deploying an EJB (even based on the Jboss example in the docs with a ./lib/ejb-client.jar, though that was for the web tier not EJB tier). 4. Using the plan below, with dual deploy dirs, the first deploy dir with common jars would be in the parent classloader for the EJBs and therefore cause no problems - right? 5. Are there plans to fix this classloading bug, since even Weblogic can resolve the jars and deploy in the proper order with no problem and no special workarounds?
Thanks, James > -----Original Message----- > From: Alex Loubyansky [mailto:[EMAIL PROTECTED]] > Sent: Friday, March 29, 2002 11:55 AM > To: James Higginbotham; [EMAIL PROTECTED] > Subject: RE: [JBoss-user] Jboss 3.0.0 beta, classpaths, and EARS > > > Hello, James. > > I am afraid you can't specify the order for jar deployment > when jars are in the same ear file. > > But I You can extract common jar files and deploy them > before jar with EJBs. But on the next server's start such > problem may rise again. To solve this problem you can create > (if not done yet) several (two is enough) directories for > deployment. They are defined in jboss-service.xml. Here is an > example: <mbean > code="org.jboss.deployment.scanner.URLDeploymentScanner" > name="jboss.deployment:type=DeploymentScanner,flavor=URL"> > <depends>jboss.system:service=MainDeployer</depends> > <attribute name="ScanPeriod">5000</attribute> > <!-- > | URLs are comma seperated and unprefixed arguments are > considered > | file URLs and resolve relative to server home unless > the given path > | is absolute. > --> > <attribute name="URLs"> > ./deploy, > ../../deploy > </attribute> > </mbean> > > Jars in ./deploy will be deployed first and jars in > ../../deploy will be deployed after them. > > alex > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of > James Higginbotham > Sent: Friday, March 29, 2002 5:37 PM > To: [EMAIL PROTECTED] > Subject: [JBoss-user] Jboss 3.0.0 beta, classpaths, and EARS > > > Hello all! My apologies for a possible duplicate post to this > list, but I did a search and manual walk of the Geocrawler > archives first. Here is the problem: > > I have an ear file with 1 EJB that I am porting to Jboss from > Weblogic (with no weblogic-specific stuff). The EJB's > manifest.mf declares a class-path (with the required C/R at > the end) with a list of 5 jars that are in the ear. It seems > that JBoss 3.0.0 beta is deploying the jars in 2 groups - > some before and some after the EJB, so not all the jars are > in JBOSS/tmp/deploy. > > Here is the manifest: > > Class-Path: common.jar log4j.jar castor.jar jdbc-se2.0.jar > jta1.0.1.jar > > Here is the output from the server's logs: > > 2002-03-29 09:19:18,046 INFO > [org.jboss.deployment.MainDeployer] Deploying: > file:/C:/bmiroot/BuildTools/jboss_tomcat/deploy/bmiapp.ear > 2002-03-29 09:19:18,086 INFO > [org.jboss.deployment.EARDeployer] Init J2EE application: > file:/C:/bmiroot/BuildTools/jboss_tomcat/deploy/bmiapp.ear > 2002-03-29 09:19:18,346 INFO > [org.jboss.deployment.MainDeployer] Deploying: > file:/C:/bmiroot/BuildTools/jboss_tomcat/tmp/deploy/101.log4j.jar > 2002-03-29 09:19:18,366 INFO > [org.jboss.deployment.MainDeployer] Deploying: > file:/C:/bmiroot/BuildTools/jboss_tomcat/tmp/deploy/96.castor.jar > 2002-03-29 09:19:18,406 WARN > [org.jboss.deployment.MainDeployer] The manifest entry in > file:/C:/bmiroot/BuildTools/jboss_tomcat/tmp/deploy/96.castor. > jar references URL file:/C:/bmiroot/BuildTools/jbo > ss_tomcat/tmp/deploy/xerces.jar, which could not be opened, > entry ignored 2002-03-29 09:19:18,406 WARN > [org.jboss.deployment.MainDeployer] The manifest entry in > file:/C:/bmiroot/BuildTools/jboss_tomcat/tmp/deploy/96.castor. > jar references URL file:/C:/bmiroot/BuildTools/jbo > ss_tomcat/tmp/deploy/jdbc-se2.0.jar, which could not be > opened, entry ignored 2002-03-29 09:19:18,406 WARN > [org.jboss.deployment.MainDeployer] The manifest entry in > file:/C:/bmiroot/BuildTools/jboss_tomcat/tmp/deploy/96.castor. > jar references URL file:/C:/bmiroot/BuildTools/jbo > ss_tomcat/tmp/deploy/jndi.jar, which could not be opened, > entry ignored 2002-03-29 09:19:18,406 WARN > [org.jboss.deployment.MainDeployer] The manifest entry in > file:/C:/bmiroot/BuildTools/jboss_tomcat/tmp/deploy/96.castor. > jar references URL file:/C:/bmiroot/BuildTools/jbo > ss_tomcat/tmp/deploy/jta1.0.1.jar which could not be opened, > entry ignored > > <Interesting stuff> > > 2002-03-29 09:19:18,426 INFO > [org.jboss.deployment.MainDeployer] Deploying: > file:/C:/bmiroot/BuildTools/jboss_tomcat/tmp/deploy/100.jta1.0.1.jar > (Below, the manifest in the EJB is being processed, before > the files are copied. They are copied below): 2002-03-29 > 09:19:18,446 INFO [org.jboss.deployment.MainDeployer] > Deploying: > file:/C:/bmiroot/BuildTools/jboss_tomcat/tmp/deploy/95.Directo > ryServiceBean.jar > 2002-03-29 09:19:18,466 WARN > [org.jboss.deployment.MainDeployer] The manifest entry in > file:/C:/bmiroot/BuildTools/jboss_tomcat/tmp/deploy/95.Directo > ryServiceBean.jar references URL file:/C:/bmiroot/ > BuildTools/jboss_tomcat/tmp/deploy/lib/common.jar which could > not be opened, entry ignored 2002-03-29 09:19:18,466 WARN > [org.jboss.deployment.MainDeployer] The manifest entry in > file:/C:/bmiroot/BuildTools/jboss_tomcat/tmp/deploy/95.Directo > ryServiceBean.jar references URL file:/C:/bmiroot/ > BuildTools/jboss_tomcat/tmp/deploy/lib/log4j.jar which could > not be opened, entry ignored 2002-03-29 09:19:18,486 WARN > [org.jboss.deployment.MainDeployer] The manifest entry in > file:/C:/bmiroot/BuildTools/jboss_tomcat/tmp/deploy/95.Directo > ryServiceBean.jar references URL file:/C:/bmiroot/ > BuildTools/jboss_tomcat/tmp/deploy/lib/castor.jar which could > not be opened, entry ignored 2002-03-29 09:19:18,486 WARN > [org.jboss.deployment.MainDeployer] The manifest entry in > file:/C:/bmiroot/BuildTools/jboss_tomcat/tmp/deploy/95.Directo > ryServiceBean.jar references URL file:/C:/bmiroot/ > BuildTools/jboss_tomcat/tmp/deploy/lib/jdbc-se2.0.jar which > could not be opened, entry ignored 2002-03-29 09:19:18,546 > WARN [org.jboss.deployment.MainDeployer] The manifest entry > in > file:/C:/bmiroot/BuildTools/jboss_tomcat/tmp/deploy/95.Directo ryServiceBean.jar references URL file:/C:/bmiroot/ BuildTools/jboss_tomcat/tmp/deploy/lib/jta1.0.1.jar which could not be opened, entry ignored 2002-03-29 09:19:18,616 INFO [org.jboss.ejb.EJBDeployer] Deploying ObjectManager 2002-03-29 09:19:18,646 INFO [org.jboss.ejb.EJBDeployer] Deploying ObjectQueryManager 2002-03-29 09:19:18,895 ERROR [org.jboss.system.ServiceController] JMRuntimeException thrown during ServiceProxy operation create on mbean jboss.j2ee:service=EJB,jndiName=com.betweenmarkets.registry.e bxml.ObjectQueryManagerHome java.lang.NoClassDefFoundError: com/betweenmarkets/util/StringMarshaller (Now, it copies the rest of the jars in the EAR - too little, too late) 2002-03-29 09:19:19,485 INFO [org.jboss.deployment.MainDeployer] Deploying: file:/C:/bmiroot/BuildTools/jboss_tomcat/tmp/deploy/99.jdbc-se2.0.jar 2002-03-29 09:19:19,505 INFO [org.jboss.deployment.MainDeployer] Deploying: file:/C:/bmiroot/BuildTools/jboss_tomcat/tmp/deploy/98.directory-service .jar 2002-03-29 09:19:19,535 INFO [org.jboss.deployment.MainDeployer] Deploying: file:/C:/bmiroot/BuildTools/jboss_tomcat/tmp/deploy/97.common.jar 2002-03-29 09:19:19,545 INFO [org.jboss.deployment.EARDeployer] Deploying J2EE application: file:/C:/bmiroot/BuildTools/jboss_tomcat/deploy/bmiapp.ear </Interesting stuff> I'm not concerned with the error messages from castor.jar, but I am concerned tht the EJB is trying to be deployed before the common.jar is deployed. So, is this a known issue, is there a workaround, or am I just missing something? I had this EJB working at some point, but now it seems to copy the jars out of order and fails to deploy the EJB (based on the web admin pages on port 8082). Any help is appreciated! Thanks, James _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
