Home/ Questions/Q 8150661
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-06T15:07:54+00:00

I have configured the loading of the properties file as shown below (Spring 3.1)

  • 0

I have configured the loading of the properties file as shown below (Spring 3.1)

my-spring-xml

<context:component-scan base-package="com.mypackage"/>
<context:property-placeholder location="file:///C:/temp/application.properties"/>

web.xml

<context-param>
        <param-name>contextConfigLocation</param-name>
        <param-value>       
        /WEB-INF/my-spring-xml
        </param-value>
    </context-param>

application.properties

expirationOffset = 777

In my java class i have declared the property as follows:

private @Value("${expirationOffset}") String propertyValue;

For some reason the value is not being initialised. When i run the following statement:

System.out.println("VALUE - " + propertyValue);

The output is always

16:03:02,355 INFO  [stdout] (http--127.0.0.1-8080-1) VALUE - ${expirationOffset}

I have tried to move the properties file in to the war file to try and access it while it is in the classpath but still the same problem. Here is how i access it from the classpath.

<context:property-placeholder location="classpath:/conf/application.properties"/>

Ideally i would like to keep the properties file outside the war file as i would not want to have to rebuild the war file because of a simple property change.

Have i missed something?

Edit

I removed the msm-spring.xml initialisation paramters from this context: 

<context-param>
            <param-name>contextConfigLocation</param-name>
            <param-value>       
            /WEB-INF/my-spring-xml
            </param-value>
        </context-param>

and moved it to the servlet context as shown below. 

<listener>
        <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
    </listener>

    <servlet>
        <servlet-name>myservice</servlet-name>
        <servlet-class>org.springframework.ws.transport.http.MessageDispatcherServlet</servlet-class>
        <init-param>
            <param-name>contextConfigLocation</param-name>
            <param-value>
            /WEB-INF/my-spring-xml
            </param-value>          
        </init-param>
    </servlet>

The above change seems to have fixed as i am now getting the correct value. I thought the way i had originally was that i had it on the application context meaning that it will be available throughout the application/webapp.

What is the difference in having the msm-spring in the either of 3 i have listed above?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    This is a bit of speculation based on the information you have provided:

    You probably don’t have the <context:property-placeholder.. in your Root Web Application context – the one loaded by ContextLoaderListener, instead you may be having it in the web context(loaded by Dispatcher servlet). Can you please confirm this.

    Update: Based on the comment, the issue seems to have been that the <context:propert-placeholder.. was defined in the Root Web application context, but being referred to in a component from Web Context.

    The fix is to move the propertyplaceholder to the web context (one defined through MessageDispatcherServlet) in this case.

    • 0