ansaurus

Question

Trying to setup externalizing properties in spring

Answer 1

+1 A:

Try this

<bean id="propertyConfigurer" class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
<property name="location" value="src/main/config/jdbc.properties" />
</bean>

c0mrade 2010-03-26 15:01:10

This only works if the final, built project puts jdbc.properties under `src/main/config` (which would be unlikely and irregular)

matt b 2010-03-26 15:21:32

@matt b what about this article? http://www.javaworld.com/javaworld/jw-12-2005/jw-1205-maven.html?page=1

c0mrade 2010-03-26 15:27:49

This doesn't work ..

Gandalf StormCrow 2010-03-26 15:46:25

@c0mrade, what about that article? You are correct that the stated convention is for "configuration files" to go in src/main/config. What I am referring to is the fact that when you package the application, the config files are *not* packaged in a folder named `src/main/config` in the packaged file (jar/war/etc.). Therefore your answer only works when you run the application within the source code, or when `src/main/config` is in the classpath (which it is not by default). The correct prefix is to use `classpath:` or another location.

matt b 2010-03-26 17:05:46

Also if you want to refer people to what the convention is, better to refer to http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html than a javaworld article from 2005.

matt b 2010-03-26 17:08:18

@matt b you're right abou that but maven guide also says `src/main/config Configuration files`

c0mrade 2010-03-26 17:19:16

I don't think you're understanding why this won't work. When you run the application, src/main/config does not exist (unless you've set up special packaging with something like the appassembler plugin).

matt b 2010-03-26 17:23:16

@matt b I apologize :D I didn't see the date, and yes I checked the war contains only properties in resources .. not in config

c0mrade 2010-03-26 17:31:16

Answer 2

+1 A:

I'm building my project with maven so according to maven way, config should be in src/main/conf

Actually, configuration data should generally go in src/main/resources, that way it will be on the classpath and you can reference your property file like:

<property name="location" value="classpath:jdbc.properties" />

Kevin 2010-03-26 15:03:28

@Kevin actually configuration should be in src/main/config and resources should be in src/main/resources http://www.javaworld.com/javaworld/jw-12-2005/jw-1205-maven.html?page=1

c0mrade 2010-03-26 15:05:13

@c0mrade arguably configuration files like these are "resources"

matt b 2010-03-26 15:22:09

@matt b yes arguably, you say it should go to resources I think it should go into config, after all resources are probably already full of something

c0mrade 2010-03-26 15:32:47

This doesn't work as well .. not if I even put the properties file in src/main/resources ..

Gandalf StormCrow 2010-03-26 15:46:56

Kevin's answer is exactly what my set-up is for multiple projects. I have a runtime.properties file in src/main/resources and a propertyConfigurer bean. The only difference is that mine uses the 'locations' property:<bean id="propertyConfigurer" class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"> <property name="locations"> <list> <value>classpath:runtime.properties</value> </list> </property> </bean>

elduff 2010-03-26 15:54:45

Answer 3

+1 A:

I think it is not quite clear as to what a "config file" means. I am thinking it is the config files used by the other maven plugins (such as surefire plugins, assembly plugins etc).

Surely in the 10+ web app projects that I have worked the bean files, jdbc.properties files have all been under src/main/resources

Calm Storm 2010-03-26 15:11:39

ansaurus

tags:

views:

answers:

Trying to setup externalizing properties in spring

related questions