Of course, datasources.xml is the purvue of the J2EE Deployer role, not of
the developers, but purity aside, not all Orion apps are delivered to
sophisticated deployment environments with a full complement of skilled
staff. I'm sure a lot of us have spent some time trying to "pre-deploy"
things so that just tossing an .ear at Orion will do everything related to
deployment.
As far as datasources.xml is concerned, the only solution we could come up
with that works is to make the deployment directory a subdirectory of the
application directory.
Something like this, in our server.xml, does the trick:
<application name="myapp" path="../applications/myapp.ear"
deployment-directory="../applications/myapp/orion" />
datasources.xml winds up being unpacked directly into the deploment
directory.
P. Pontbriand
Canlink Interactive Technologies Inc.
----- Original Message -----
From: "Yves Bossel" <[EMAIL PROTECTED]>
To: "Orion-Interest" <[EMAIL PROTECTED]>
Sent: Thursday, May 17, 2001 9:53 AM
Subject: deploying additional files
> Hello,
>
> I am trying to pack my application in as independently as possible of the
> deployment configuration (i.e. paths).
> data-sources.xml and principals.xml get packed into the application's
> META-INF.
> However, unlike orion-application.xml, data-sources.xml does not get
copied
> into <orion>/application-deployments/<my-app>.
>
> Is there a deployment-path-independent way to pack such files and to
specify
> in their location in the deployment descriptors ?
> Is there a way to get Orion deploy additional files in the META-INF (Orion
> seems to look first there for needed deployment files)?
>
>
> My goal is to have to modify the least possible number of configuration
> files at deployment.
>
>
> Thanks
>
> > Yves Bossel L.
> > Programmer
> > www.neoris.com - Business Technology Partners
> > Edificio Birmann 24, Sanchez Fontecilla 310, piso 7 (esq. Callao)
> > Las Condes, Santiago; CHILE
> > oficina: (56-2) 426-1260
> > email: [EMAIL PROTECTED]
> >
>
>
