Kyle, All though the pain of refactoring might be too great for you at the moment, you could consider giving unique names to each Bean's deployment descriptors (e.g. Appname-ejb-jar.xml and Appname-weblogic-ejb-jar.xml). It's then pretty straightforward to include these in your Ant <ejbjar> tasks which create the EJB jars, and would solve the problem of collisions. We took that approach in my shop and it works pretty well.
Matt -----Original Message----- From: Kyle Adams [mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 11, 2002 11:13 AM To: [EMAIL PROTECTED] Subject: Promoting EARs I've been asked to write scripts to automate our promotion process (from Dev to Test to Production). We deploy our applications as EARs, typically containing one WAR and multiple EJB JARs. Our promotion process consists of extracting the deployment descriptors, making necessary changes to move from one environment to the next, placing the modified DDs back in the archives, and FTPing everything up. Currently we do this by hand. Looking at the core set of Ant tasks, I see some problems with automating the process - I can unear the application, then unzip all of the archives it contains, and use a <patternset> to only extract deployment descriptors. The problem is that all of our EJB DDs have the same names - ejbjar.xml and weblogic-ejbjar.xml. Thus, they end up over-writing each other on extraction. Thus, I'm at a loss as to easy ways to extract files (with the same name) from multiple archives in such a way that they don't stomp all over each other. I could write my own task, creating separate subdirectories within the destination directory to separate out the EJB DDs, but I wanted to check if anyone else has addressed this issue before. Thanks, Kyle Adams Java Developer Gordon Food Service -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
