Well, multiple jaws.xml files work fine when I dont stick extra jars in the classpath by accident. never mind the treatise below this. -----Original Message----- From: Castro, David [mailto:[EMAIL PROTECTED]] Sent: Friday, January 26, 2001 2:19 PM To: 'jBoss' Subject: RE: [jBoss-User] is it possible to include multiple jaws.xml file s in .ear??? -- I think this is a bug Hmmm. it does seem to be a bug. The issue is that in org/jboss/ejb/ContainerFactory.java, the call to load up the ejb-jar.xml and jboss.xml is made first (line 341: ApplicationMetaData metaData = efm.load();) using a temporary classloader which is only aware of the correct jar file. The loading of the jaws.xml file is handled by the EntityContainer using its normal classloader. Unfortunately there are lots of temporary jar files in the normal classpath which supercede the correct jar file, and so the wrong jars.xml is loaded. the fix would seem to be either: 1. get all the extra jar files out of the normal classpath or 2. use a temporary classloader to load the jaws.xml file is anybody aware of this problem? should I try to put this in bugzilla? I will probably try fix no. 2 as a stopgap in my own code since it looks easier (I dont know how all the extra crap is getting into the regular classpath, nor do I have any idea how to fix it). -----Original Message----- From: Castro, David [mailto:[EMAIL PROTECTED]] Sent: Friday, January 26, 2001 12:06 PM To: 'jBoss' Subject: [jBoss-User] is it possible to include multiple jaws.xml files in .ear??? Is this a bug? Normally, when you deploy an ejb jar file, you can include ejb-jar.xml, jaws.xml, jboss.xml. So in making my ear file, where I have 3 entity jar files, each jar has ejb-jar.xml, jaws.xml, jboss.xml. However, I noticed that during deployment of each ejb jar file, it seemed to be using the same jaws.xml every time. looking through the code, I noticed in org/jboss/ejb/plugins/jaws/metadata/JawsXmlFileLoader.java, line 64, where the jaws.xml file is loaded, that we are simply looking in the classpath for the name META-INF/jaws.xml. Assuming that all ejb jars are added to the classpath at one time, and that all use the same classloader, it seems like we would be loading the same jaws.xml every time even if there was one in every ejb jar. There doesn't seem to be the same problem with the ejb-jar.xml though. -- -------------------------------------------------------------- To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] List Help?: [EMAIL PROTECTED] -- -------------------------------------------------------------- To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] List Help?: [EMAIL PROTECTED] -- -------------------------------------------------------------- To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] List Help?: [EMAIL PROTECTED]
