Aaron, The idea is that one application may be deployed on many servers, and therefore the deployment descriptor is *per app, per server*. The deployment descriptors are used to customise a deployment on that server.
This notion fits in with sun's idea of J2EE roles (ppl who help develop the application.) Read about roles here: http://java.sun.com/j2ee/tutorial/1_3-fcs/doc/Overview5.html#65592 If you had your deployment files working, and then you upgraded the application (ie installed a newer version - perhaps a web-app version of your ejbs) you would not want the deployment descriptors overridden except where they dont exist (for the new parts of the application). If in development you feel that this is a problem - then add another ant target to delete the deployment descriptors from the deployment directory. Cheers, Scott -- Scott Farquhar :: [EMAIL PROTECTED] Atlassian :: http://www.atlassian.com Supporting YOUR J2EE World Aaron Tavistock wrote: > Mike - > > Since this is a generated file in a deployment directory shouldn't it always > be overwritten if there is a change in one of the package deployment > descriptors? The only reason it would be a pain in the ass is if you > changed the generated file to suit your needs and did not change the one you > bundle with your package. > > If this is intended behavior, IMHO it is significantly less intuitive. Its > kind of like saying a class should only be recompiled if you delete the > class before recompiling, where one would expect that changing the source > would be enough. > > Just my two cents. > > Aaron Tavistock > > -----Original Message----- > From: Mike Cannon-Brookes [mailto:[EMAIL PROTECTED]] > Sent: Friday, December 21, 2001 2:13 AM > To: Orion-Interest > Subject: Re: CMP Entity Bean Craziness > > > You're not special at all (well you may be - but that's a different > story ;)) - what you describe is exactly the intended behaviour of the > server. > > You're editing the deployment files in your EAR which are only used _IF > AND ONLY IF_ there is no existing deployment file. Otherwise the > existing deployment file is used, and the one in the EAR ignored. > > This behaviour is as it should be because otherwise you'd end up > overwriting your deployment settings all the time which would be a royal > pain in the ass. > > HOWEVER to do what you want, simply delete the deployment directory and > your edited files will be copied and used. You will see a message on the > console telling you that the deployment file has been copied. > > Hope this helps clear things up. > > Cheers, > Mike > >
