{"id":1325,"date":"2012-06-28T22:00:00","date_gmt":"2012-06-28T22:00:00","guid":{"rendered":"http:\/\/www.javacodegeeks.com\/2012\/10\/spring-3-1-profiles-and-tomcat-configuration.html"},"modified":"2012-10-22T05:24:43","modified_gmt":"2012-10-22T05:24:43","slug":"spring-31-profiles-and-tomcat","status":"publish","type":"post","link":"https:\/\/www.javacodegeeks.com\/2012\/06\/spring-31-profiles-and-tomcat.html","title":{"rendered":"Spring 3.1 profiles and Tomcat configuration"},"content":{"rendered":"
Spring 3.1 introduced very useful feature called profiles<\/strong><\/a>. Thanks to that its easy to build one package that can be deployed in all environments (development, test, production and so on).<\/span><\/p>\n

By defining system property spring.profiles.active<\/strong> Spring allows us to create different beans depending on active profile name using XML configuration or @Profile<\/a> annotation. As we all know system properties can be used in Spring XML files and we will take advantage of that. <\/p>\n

In this post I will show how to use Spring profiles to create one package for all environments and how to run it on Apache Tomcat. <\/p>\n

Example architecture<\/strong> <\/p>\n

I think the most common and wanted architecture is when applications deployed on dev, test and production differ only in used properties file containing configuration. WAR contains configuration for all environments and correct one is chosen during runtime. So it is the best if in application resources we have files like: <\/p>\n

src\r\n  main\r\n    resources\r\n      - config_dev.properties\r\n      - config_production.properties\r\n        ...\r\n<\/pre>\n
Configuring Spring property placeholder<\/strong>        
 
<\/div> <\/div><\/p>\n
In order to load properties files in Spring we use <context:property-placeholder \/><\/code> or @PropertySource<\/a> annotation. In my example I will follow XML configuration approach for loading properties file:         <\/p>\n
<?xml version='1.0' encoding='UTF-8'?>\r\n<beans xmlns='http:\/\/www.springframework.org\/schema\/beans'\r\n    xmlns:xsi='http:\/\/www.w3.org\/2001\/XMLSchema-instance'\r\n    xmlns:context='http:\/\/www.springframework.org\/schema\/context'\r\n    xsi:schemaLocation='http:\/\/www.springframework.org\/schema\/beans\r\n\r\nhttp:\/\/www.springframework.org\/schema\/beans\/spring-beans-3.1.xsd\r\n\r\nhttp:\/\/www.springframework.org\/schema\/context\r\n\r\nhttp:\/\/www.springframework.org\/schema\/context\/spring-context-3.1.xsd'>\r\n\r\n    <context:property-placeholder location='classpath:config_${spring.profiles.active}.properties' \/>\r\n\r\n<\/beans>\r\n<\/pre>\n
Configuring Tomcat<\/strong>        <\/p>\n
Now its time to tell Tomcat which profile is active. There at least ways to do that:         <\/p>\n