Thanks Brandon for confirming the general approach.
Thanks Mark for the suggestion to use Context/Environment parameters. I
think that properties files would be easier, in that each application can
have its own properties files maintained and source controlled separately.
I wanted to confirm tha
On Thu, Jul 17, 2014 at 05:01:32PM -0400, Brandon M. Wagner, Triple Tech Inc.
wrote:
>
> > On Jul 17, 2014, at 3:54 PM, Toby Lazar wrote:
> >
> > Hi,
> >
> > Say I have an application that uses a properties and/or XML file that
> > changes per environment. I'd like to create the WAR once and
> On Jul 17, 2014, at 3:54 PM, Toby Lazar wrote:
>
> Hi,
>
> Say I have an application that uses a properties and/or XML file that
> changes per environment. I'd like to create the WAR once and promote it
> from TES -> STAGE -> PROD without modification. Is this approach sensible?
> Is there
Hi,
Say I have an application that uses a properties and/or XML file that
changes per environment. I'd like to create the WAR once and promote it
from TES -> STAGE -> PROD without modification. Is this approach sensible?
Is there a recommended approach for externalizing it? Is it safe to
appen
