You can place your orion-*.xml files alongside their *.xml counterparts.
(eg, principals.xml and orion-application.xml alongside application.xml).
Note though that if the application has already been deployed, then these
files won't be copied over the existing ones. They're only used in the case
of a 'fresh install'.
>From: "Rian Schmidt" <[EMAIL PROTECTED]>
>Reply-To: Orion-Interest <[EMAIL PROTECTED]>
>To: Orion-Interest <[EMAIL PROTECTED]>
>Subject: Deployment xml files in ear file? If so, where?
>Date: Mon, 26 Mar 2001 14:47:50 -0800
>
>Hi all,
>
>Firstly, we're having great luck with our adventures with Orion. Most
>everything works as advertised, and the performance is great-- particularly
>the CMP EJB stuff. Just thought I'd spew a little positivity.
>
>Is there some way to include the application-deployments XML files with an
>application? By that I mean, fer instance, we've made all kinds of
>modifications to orion-ejb-jar.xml to deal with our OR relationships, the
>legacy database name mappings, etc. orion-application.xml has a bunch of
>custom settings too. Were either of those to get wiped by an overzealous
>Orion, we'd be... sad. So, we're gonna back them up, but...
>
>Do we need to manually make those changes after deploying the application
>on
>another machine? That seems a little goofy. I'd hate to have to say to a
>customer "OK, start it up, and then stop it, open this file up and
>everywhere it says requestId, well, change that to request_id, blah blah,
>and then restart it."
>
>Thanks,
>Rian
>
>--
>Rian Schmidt
>[EMAIL PROTECTED]
>
>
>
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
