Hi Eric, Um, the answer is probably not, but you can reference another jar file by adding something like the following to your manifest.mf file: Class-Path: ./ext/MyCustSpecific.jar In this case, one puts the MyCustSpecific.jar file in deploy/lib to indicate it is not one of the normal ejb jar files. You could try putting the jboss.xml there, but I suspect it won't work as hoped.
Let us know if this idea works for you. Maybe others would like to use it too. Cheers, Craig --------------------------- Original Message From: "Eric Kaplan" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Date: Wed, 30 Jan 2002 10:12:08 -0500 Subject: [JBoss-user] Configuration Issue I apologize in advance if this isn't the appropriate forum for this, but... Right now, when we create our ear file, we jar up various sets of beans with the META-INF/ejb-jar.xml and META-INF/jboss.xml files. However, depending upon the customer, they are going to want to specify different connection pools for the jndi lookups in the jboss.xml. Can you make two separate jars, one with everything but the jboss.xml, and another jar just with the jboss.xml, so individual customers can easily override these settings? Thanks Eric _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
