PropertyPlaceholderConfigurers loading after parameterized DataSource bean

Question

At the top of my application context I declare a PropertyPlaceholderConfigurer

...
<context:annotation-config/>

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

Later on I declare a datasource bean parameterized by properties from that properties file

<bean id="someDataSource" class="oracle.jdbc.pool.OracleDataSource" destroy-method="close">
    <property name="connectionCachingEnabled" value="true"/>
    <property name="URL" value="${database.url}"/>
    <property name="user" value="${database.user}"/>
    <property name="password" value="${database.password}"/>
</bean>

During deployment I notice that the datasource bean is created and a connection is attempted to be established BEFORE the PropertyPlaceholderConfigurer is initialized. That's causing my datasource parameterizations to not be populated.

Any idea why this might be happening?

Is there a specific order of creation for beans? Are certain beans always initialized before others? Is there a way to ensure that the PropertyPlaceholderConfigurer is loaded before all other beans?

It is loaded before all other beans unless you are using the datasource in some other bean that is needed very early on in your startup sequence. — M. Deinum, Jun 19 '15 at 06:27

score 1 · Accepted Answer · edited May 23 '17 at 12:03

1

It turns out that one of the beans I defined is a MapperScannerConfigurer for mybatis that references a sqlSessionFactory.

The MapperScannerConfigurer can initialize prior to any PropertyPlaceholderConfigurer if it's initialized with deprecated bean properties

To correct the behavior, the sqlSessionFactory has to be referenced using a different bean property.

See this related post for more details

edited May 23 '17 at 12:03

Community

1
1

answered Jun 19 '15 at 13:03

Daniel Lawry

85
5

After three days of tracking this down in my own application, it all seems so simple now :) Thanks for your contribution! – Dakota Brown Nov 16 '15 at 19:03

score 0 · Answer 2 · answered Jun 18 '15 at 19:41

0

You need to move the <context:property-placeholder location="classpath:foo.properties"/> ahead of <context:annotation-config/>

<context:property-placeholder location="classpath:foo.properties"/> <context:annotation-config/>

answered Jun 18 '15 at 19:41

Gabriel J

9
2

Ordering doesn't matter in this case. – M. Deinum Jun 19 '15 at 06:27
@Gabriel J Thank you for the suggestion. It turned out to be related to how a Mybatis related bean was created. You can see my post below and the related link if you're curious – Daniel Lawry Jun 19 '15 at 13:06

PropertyPlaceholderConfigurers loading after parameterized DataSource bean

2 Answers2