Hrm. That's unfortunate. Our Ant build script largely works unmodified on
a number of different application servers thus far, but now I'll have to
have an orion-specific extra clean step, since removing the EAR does not, in
and of itself, clear out the rest of the application as it does elsewhere.
Thanks,
- Geoffrey
: -----Original Message-----
: From: Mike Cannon-Brookes [mailto:[EMAIL PROTECTED]]
: Sent: Wednesday, November 21, 2001 6:00 PM
: To: Orion-Interest
: Subject: Re: orion-ejb-jar and other such descriptors
:
:
: Geoffrey,
:
: This is the expected behaviour. The deployment descriptors are only
: copied from the EAR after a clean deploy. Otherwise Orion might
: overwrite deployment descriptors that you had edited.
:
: Cheers,
: Mike
:
: --
: Mike Cannon-Brookes :: [EMAIL PROTECTED]
:
: Atlassian :: http://www.atlassian.com
: Supporting YOUR J2EE World
:
:
: On Thu, 2001-11-22 at 07:03, [EMAIL PROTECTED] wrote:
: > I've put an orion-ejb-jar.xml in the EJB Jar's META-INF.
: If I clean out the
: > Orion/application-deployment and Orion/applications versions of the
: > application, and deploy to Orion, the file copies into the
: appropriate place
: > and takes effect. If I deploy on top of an existing EAR,
: the redeploy
: > process doesn't seem to replace the existing
: orion-ejb-jar.xml file. I
: > suspect this is probably happening with other descriptors,
: but this is the
: > one that I just tested thoroughly recently, to ensure that I wasn't
: > imagining that.
: >
: > Is there any way to ensure that the file does get deployed
: along with the
: > rest of the EAR? Am I missing something?
: >
: > - Geoffrey
: > __________________________________________________________
: > Geoffrey Wiseman: Internet Applications Manager
: > Medium One
: > t. 416.977.2101 x. 529
: > http://www.mediumone.com/
: > __________________________________________________________
: > Think it. Build it. Work it.
: >
: >
: >
:
:
:
