Thanks for the prompt replies :-) I didn't precise I was not at an Application layer, but in a layer above. I confirm that on the Application layer, Spring answers really well about the problematic.
For example, my packaging will produce a complete archive with tomcat bundled into it. In the tomcat configuration, I have to pack some load balancing configuration props (jvmRoute attribute in server.xml for example). These properties are "environnment dependent" too (on dev envs, I won't have to use load balancing, but in production env, I'll have to) Frédéric On Fri, Feb 4, 2011 at 2:00 AM, Wendy Smoak <[email protected]> wrote: > On Thu, Feb 3, 2011 at 6:48 PM, Frederic Camblor <[email protected]> > wrote: > > Nobody has any piece of advice against these options ? :( > > When you tell us you can't change anything, there's not much to say. > > Either move the configuration out of the war, or put it *all* in there > and use something (like Spring) that can sense which environment it is > running in and select the right config file. In any case, you want > *one* artifact that can be used in the different environments. > > -- > Wendy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
