> 1) Not using the 'applications' directory for deployment. Even though we still put stuff in an applications directory, that's merely a naming convention--it's not under the $WL_HOME, so nothing gets auto-deployed (I believe we have auto deploy turned off in all environments). I think we're all set on this point.
> 2) Using the weblogic ant <wldeploy> taskdef > http://edocs.bea.com/wls/docs81/deployment/tools.html#1000477 I took a brief look at this tool, and I'm pretty familiar with the corresponding WL 7 tool, since that's what we're using to automate our hot deploys. Now then, bear with me here, because I really am trying to understand :-) If I understand correctly, in your process you do something like: <wldeploy action="deploy" source="myEJB-1.0.1.jar" name="myEJB" user="a" password="a" adminurl="t3://localhost:7001"> Even though the EJB previously deployed as "myEJB" was myEJB-1.0.0.jar, the deploy action above successfully redeploys myEJB-1.0.1.jar in place of the older jar, correct? > Using the proprietary <context-root> element in the > appropriate weblogic.xml deployment descriptor. To begin with, most all of our applications are deployed in EARs - we have very few WARs or EJBs deployed outside an EAR (meaning that we'd need to dynamically generate the application.xml from the POM - not impossible, just something else to script out). My understanding of <context-root> within an EAR is that BEA suggests setting that in the application.xml, where it is relative to the root of the EAR. I don't think it would do anything to help or hinder getting around the problem of ever-changing JAR names. Am I missing something there about how you're using <context-root>? Thanks, Kyle _____ Kyle Adams | Java Developer | Gordon Food Service | 616-717-6162 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
