If it's data that is different, then you can have different ant readers.
If it's the code or properties files, then you can maintain patches.
On Sat, 20 Apr 2013 02:31:16 +0530, Matthew Bertolini
<mbertol...@mypublisher.com> wrote:
I was wondering how everyone tackles environment specific configurations
in OFBiz. We deploy the same codebase to multiple environments (local,
development, QA, and production) and we have different settings for
things like database connections, server settings, security settings,
etc. What are the best practices for maintaining different settings for
each environment?
In other Java applications I maintain, I have an environment variable
(app.env) that I set a runtime with something like 'dev' or 'prod' which
get used to load properties files named 'settings_dev.properties' and
'settings_prod.properties'. In the code (or in a spring file) can can
substitute the ${app.env} with the environment name and it will load the
correct configuration. Is something like this possible with OFBiz
configuration/XML files? Is there a pre-baked solution already in place?
Thanks,
Matt Bertolini
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
