On Mon, 2003-10-27 at 13:56, Kyle Adams wrote: > > But even in deployment situations you can provide whatever additional > > information you like. Weblogic is not going to be confused about version > > names in the jar and you can stuff as much meta info as you like into the > > JAR. > > 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
You can use the jar override feature if you really want to have versionless. It's documented in the user guide. You can also specify specific names of the JARs you use in your POM, not recommended but possible. > 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. > > The POM probably wouldn't even be a good location for this metadata, because that > metadata would vary depending on what environment (Dev, Test, Production) > myEJB-1.0.1.jar is being deployed in. For example, is it a clustered environment? > If so, then in WebLogic you need to target a cluster, not a managed server, which > may have different naming conventions than the managed servers targeted in previous > environment. > > It seems to me that Maven, by forcing versioning metadata to be contained in the JAR > name, also forces a manual deployment process. I'd be happy to change the process, > as long as it can stay automated (and ideally taking advantage of hot re-deploy > capabilities in most modern J2EE containers). It doesn't force manual deployment at all. I have automated deployments with versioned JARs and I don't have any problems. Maybe this is different with WebLogic. > I'd love to hear what Vincent has to say, if he's encountered these problems, and > how he's resolved them. I assume he's also active on this list? > > 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] -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
