> -----Original Message----- > From: Kyle Adams [mailto:[EMAIL PROTECTED] > Sent: Monday, October 27, 2003 1:56 PM > To: [EMAIL PROTECTED] > Subject: Re: JAR Repository and File Names > > Whether or not WebLogic gets "confused" is a matter of > opinion. When an EJB (or WAR or EAR or whatever) is > deployed, WebLogic specifies a path for that deployable: > > /home/weblogic/mydomain/applications/myEJB.jar > > If the version information is included in the file name, that > means everytime you want to deploy a new version in WebLogic, > you have to remove the old deployable, and re-configure the > new deployable: > > /home/weblogic/mydomain/applications/myEJB-1.0.1.jar > > changes to: > > /home/weblogic/mydomain/applications/myEJB-1.0.2.jar > > In order to automate this process, you'd have to maintain > deployment metadata for myEJB-1.0.1.jar in your POM (for > example, with WebLogic, what managed servers the EJB is > targeted to). That metadata would almost certainly change > from one J2EE container to another.
We avoid the ear/war/jar filename change issue in WebLogic 8.1 in out projects by ... 1) Not using the 'applications' directory for deployment. 2) Using the weblogic ant <wldeploy> taskdef http://edocs.bea.com/wls/docs81/deployment/tools.html#1000477 3) Using the proprietary <context-root> element in the appropriate weblogic.xml deployment descriptor. This makes our deployment version neutral (whatever we deploy last is what is currently active, with no context issues). /* joakim */
