You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by stevec1979 <st...@gmail.com> on 2008/06/28 02:55:06 UTC
Deploying to different environments.
What are some best practices for deploying a service unit across multiple
environments (stage/prod/etc)?
For example, an external web service has different urls for prod and stage,
how should the binding component be defined for different environments?
I would like to avoid having to do separate packaging for stage/prod... Is
it acceptable to define a properties file and externalize environment
specific settings (service location) using a properties configurator in the
xbean.xml and place the properties file on the classpath outside of the
service assembly.
--
View this message in context: http://www.nabble.com/Deploying-to-different-environments.-tp18166246p18166246.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: Deploying to different environments.
Posted by Gert Vanthienen <ge...@skynet.be>.
L.S.,
I usually try to leverage Maven2 resource filtering technique for doing
this, but this is still done when packaging an app. However, the
xbean.xml files ServiceMix uses are just Spring configuration files, so
you can basically do anything you can do with Spring in there. If you
want externalize the properties file and put it somewhere else (i.e. not
in the SA), there's no reason why you shouldn't (be able to) do so. It
is hard for us to tell what your actual requirements are, but if your
application requires externalization, it's perfectly acceptable have
external properties files -- ServiceMix itself shouldn't even see the
difference...
Regards,
Gert
stevec1979 wrote:
> What are some best practices for deploying a service unit across multiple
> environments (stage/prod/etc)?
> For example, an external web service has different urls for prod and stage,
> how should the binding component be defined for different environments?
> I would like to avoid having to do separate packaging for stage/prod... Is
> it acceptable to define a properties file and externalize environment
> specific settings (service location) using a properties configurator in the
> xbean.xml and place the properties file on the classpath outside of the
> service assembly.
>