Maven Tests with Spring propertyPlaceHolderConfig

adam

This seemingly innocuous combination cost me almost a full day to debug. The error I was getting was:

Caused by: org.springframework.beans.factory.BeanDefinitionStoreException: Error registering bean with name 'mailSender' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Could not resolve placeholder 'smtp.host'

The configuration file was being found, however the properties were not being loaded into by the propertyPlaceHolder. The solution to this is to use the SystemClassLoader, which is not the default for the surefire plugin you can define it like this:

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<configuration>
<useSystemClassLoader>true</useSystemClassLoader>
<excludes>
<exclude>
this dummy value is to override surefire’s default
</exclude>
</excludes>
</configuration>
</plugin>
Hopefully this is helpful to people trying to use this combination of Maven and the Spring propertyPlaceHolderConfig

This entry was posted on Tuesday, April 24th, 2007 at 12:28 pmand is filed under Java. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

Leave a Reply