Spring @Value is not resolving to value from property file

Question

I've had this working in some other project before, I am just re-doing the same thing but for some reason it's not working. The Spring @Value is not reading from property file, but instead it's taking the value literally

AppConfig.java

@Component
public class AppConfig
{
    @Value("${key.value1}")
    private String value;

    public String getValue()
    {
        return value;
    }
}

applicationContext.xml:

<context:component-scan
    base-package="com.test.config" />
<context:annotation-config />

<bean id="appConfigProperties"
    class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
    <property name="location" value="classpath:appconfig.properties" />
</bean>

appconfig.properties

key.value1=test value 1

In my controller, where I have:

@Autowired
private AppConfig appConfig;

The application starts just fine, but when I do

appConfig.getValue()

it returns

${key.value1}

It doesn't resolve to the value inside the properties file.

Thoughts?

Duplicated http://stackoverflow.com/questions/11890544/spring-value-annotation-in-controller-class-not-evaluating-to-value-inside-pro and http://stackoverflow.com/questions/5275724/spring-3-0-5-doesnt-evaluate-value-annotation-from-properties — pedjaradenkovic, Apr 10 '13 at 22:29
Thanks! didn't find that thread, most the ones I found was related to the value being NULL — TS-, Apr 11 '13 at 12:55

Sachchidanand Singh · Answer 1 · 2015-07-06T06:17:41.743

74

I also found the reason @value was not working is, @value requires PropertySourcesPlaceholderConfigurer instead of a PropertyPlaceholderConfigurer. i did the same changes and it worked for me, i am using spring 4.0.3 release. I configured this using below code in my configuration file -

@Bean 
public static PropertySourcesPlaceholderConfigurer propertySourcesPlaceholderConfigurer() {
return new PropertySourcesPlaceholderConfigurer();
}

edited Jul 06 '15 at 06:17

answered Nov 27 '14 at 06:47

Sachchidanand Singh

1,356
1
12
15

you can get more information on this configuration from http://blog.codeleak.pl/2015/09/placeholders-support-in-value.html – Kishor K Dec 21 '17 at 12:52
1

FYI: You don't have to add this Bean with Spring boot 1.5.9 anymore. – realPK Feb 21 '18 at 19:49
1

@realPK looks like you do, i'm on spring 4.2.6 and still had to add it. – Florian Wicher Dec 10 '19 at 16:38
1

@FlorianWicher I was talking about Spring Boot, which I believe uses Spring framework 4.3. Reference - https://spring.io/blog/2017/11/28/spring-boot-1-5-9-available-now. – realPK Dec 12 '19 at 00:38
@Florian Wicher - May be you could try upgrading spring boot version to 2.x and you would be able to avoid this. – Sachchidanand Singh Dec 12 '19 at 06:20

score 36 · Answer 2 · answered Mar 30 '17 at 08:42

36

In my case, static fields will not be injected.

answered Mar 30 '17 at 08:42

User007

701
7
11

1

Just had to remove that `static` keyword and it's working fine now! – takanuva15 Feb 20 '20 at 20:34
Worked for me as well. It's weird because I have static fields with @Value in other classes which work just fine. – Chris Neve Aug 27 '20 at 19:49
for me i want to use static fields, how can I achieve in case of static fields – Rookie007 Oct 26 '21 at 13:14

score 20 · Accepted Answer · edited May 23 '17 at 12:10

20

Problem is due to problem in my applicationContext.xml vs spring-servlet.xml - it was scoping issue between the beans.

pedjaradenkovic kindly pointed me to an existing resource: Spring @Value annotation in @Controller class not evaluating to value inside properties file and Spring 3.0.5 doesn't evaluate @Value annotation from properties

edited May 23 '17 at 12:10

Community

1
1

answered Apr 14 '13 at 04:35

TS-

4,121
8
39
52

score 13 · Answer 4 · answered Jun 08 '18 at 00:59

13

In my case I was missing the curly braces. I had @Value("foo.bar") String value instead of the correct form @Value("${foo.bar}") String value

answered Jun 08 '18 at 00:59

Naruto Sempai

4,447
5
32
50

2

you made my day, thanks – Bassel Kh Oct 02 '21 at 14:41

Dapper Dan · Answer 5 · 2019-06-05T17:07:52.260

9

for Sprig-boot User both PropertyPlaceholderConfigurer and the new PropertySourcesPlaceholderConfigurer added in Spring 3.1. so it's straightforward to access properties file. just inject

Note: Make sure your property must not be Static

@Value("${key.value1}")
private String value;

edited Jun 05 '19 at 17:07

answered Apr 12 '18 at 13:12

Dapper Dan

802
10
21

score 4 · Answer 6 · answered Sep 09 '17 at 12:50

4

I was using spring boot, and for me upgrading the version from 1.4.0.RELEASE to 1.5.6.RELEASE solved this issue.

answered Sep 09 '17 at 12:50

craastad

5,624
5
30
44

score 2 · Answer 7 · answered Apr 20 '21 at 12:26

2

In my case, I had the lombok @AllArgsConstructor and that picked up the property as well. Deleting this annotation solved the problem.

answered Apr 20 '21 at 12:26

Ahmed Aziz

331
5
14

score 1 · Answer 8 · answered Apr 10 '13 at 22:33

1

Have a read of pedjaradenkovic's comment.

Further to the link he provides, the reason this isn't working is that @Value processing requires a PropertySourcesPlaceholderConfigurer instead of a PropertyPlaceholderConfigurer.

answered Apr 10 '13 at 22:33

Muel

4,152
1
22
32

1

PropertyPlaceholderConfigurer works just fine for me. I just needed to fix the context:component-scan in my app context xml and spring servlet xml – TS- Apr 11 '13 at 12:56
@TS what version of spring are you using, please? – Muel Apr 11 '13 at 13:15
Can't you @Autowire Environment instead? see http://stackoverflow.com/a/15562319/632293 – jediz Apr 01 '16 at 16:08

score 1 · Answer 9 · edited May 15 '21 at 07:04

@Value sometimes can take a day or a half to get resolved ;).

Here is what I did :

Add property to properties or YAML file
Make Sure MAIN CLASS IS ANNOTATED WITH @EnableAutoConfiguration OR @SpringBootApplication
CREATE AppConfig IN WHICH YOU CAN USE @Value

@Value("${PROPERTY}") private String URL;

Annotate this AppConfig with @Configuration at class level

SO FAR SETUP IS DONE NOW USE IT WHEREVER YOU WANT BY AUTOWIRING AppConfig

EXAMPLE: IN SOME SERVICE @Autowired private AppConfig appConfig; AND IN THE METHOD OF THIS SERVICE call appConfig.getUrl() to get the value of property URL from a properties file.

NOTE: DON'T TRY TO GET VALUE IN CONSTRUCTOR OF SERVICE IT WILL BE NULL.

Thank you so much - that was my point 'NOTE: DON'T TRY TO GET VALUE IN CONSTRUCTOR OF SERVICE IT WILL BE NULL.' — Tony, Feb 18 '22 at 14:41

score 0 · Answer 10 · answered Apr 27 '20 at 15:57

Please note that if you have multiple application.properties files throughout your codebase, then try adding your value to the parent project's property file.

You can check your project's pom.xml file to identify what the parent project of your current project is.

Alternatively, try using environment.getProperty() instead of @Value.

score 0 · Answer 11 · edited Aug 07 '21 at 19:58

0

Mine was casued by importing a wrong dependency. I had it imported from lombok by accident instead of "import org.springframework.beans.factory.annotation.Value;" Changing it back solved the problem

edited Aug 07 '21 at 19:58

Etienne Kaiser

2,634
8
19
29

answered Aug 07 '21 at 14:38

emily

35
1
9

Spring @Value is not resolving to value from property file

11 Answers11

Linked