externalised config?

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

externalised config?

ldeck
Hi all,

is it possible to externalise configuration for both exist-conf.xml and properties-local.xml, for example?
The advantage for this would be that the war artefact wouldn't need manipulation prior to deployment per environment.

cheers,
Lachlan

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Reply | Threaded
Open this post in threaded view
|

Re: externalised config?

Eric van der Vlist
Le lundi 16 septembre 2013 à 06:36 +1000, Lachlan Deck a écrit :
> Hi all,
>
> is it possible to externalise configuration for both exist-conf.xml
> and properties-local.xml, for example?

You can play with the configuration of the resource managers (in
web.xml) to add an external directory that will override what's inside
the war (including configuration files), see:

http://eric.van-der-vlist.com/blog/2012/10/18/installing-orbeon-forms-tomcat-and-your-application-side-by-side-on-ubuntu/

Hope this helps.

Eric

> The advantage for this would be that the war artefact wouldn't need
> manipulation prior to deployment per environment.
>
> cheers,
> Lachlan
>


--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Reply | Threaded
Open this post in threaded view
|

Re: externalised config?

Alessandro  Vernet
Administrator
Eric van der Vlist wrote
You can play with the configuration of the resource managers (in
web.xml) to add an external directory that will override what's inside
the war (including configuration files)
Exactly; and if you want to do this outside of the web.xml, to leave the latter unchanged, you can define those parameters in the app server configuration, for instance with Tomcat, adding inside the <Context> something like:

<Parameter override="false" name="oxf.resources.priority.0" value="org.orbeon.oxf.resources.FilesystemResourceManagerFactory"/>
<Parameter override="false" name="oxf.resources.priority.0.oxf.resources.filesystem.sandbox-directory" value="/path/to/your/resources"/>

Alex
--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet