On 01/03/2010 16:47, co...@sapo.pt wrote:
Hello! Actually we have a lot of different web applications with specific settings for each one, namelly: JNDI, SPRING, logging properties, JMS properties, etc... Some of these webapplication could be deployed in different TOMCAT instances. The centralization of these settings would be a major improvement to facilitate the setup task and minimize the setup time. What is the best way to implement a central file with all of these settings?
Do it at build time. So many different configuration requirements would be very difficult to do otherwise.
Putting configuration files into a source repository and writing scripts to generate multiple outputs is sometimes recommended here.
p
Thanks a lot Best Regards C.o.u.v.a --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
