Spring 4 - load property file inside the jar>war

Question

I could not load the db.properties located inside the jar (project.service.jar), which is referred by the war file (project-web.war). The output war has the jar inside WEB-INF/lib/project.service.jar. The services jar has the services and dao classes used by the web app. The jar is also used by the rest war which uses some of the services from the jar. When the war starts I could not load the db.properties located in the jar file of the services. The prop file has the datasource name to lookup in jndi.

war config

AppConfig.java

@Bean
public static PropertyPlaceholderConfigurer propertyConfigurer()
        throws IOException {
    PropertyPlaceholderConfigurer props = new PropertyPlaceholderConfigurer();
    props.setLocations(new Resource[] { new ClassPathResource(
            "application.properties") });
    return props;
}

service.jar

@Component
@Configuration
//@ComponentScan(basePackages={ "com.mgage.mvoice" })
@PropertySource(value = { "classpath:db.properties" })
public class DatabaseConfig {
    @Autowired
    Environment environment;

    private @Value(value = "${voice.datasource}") String dataSourceString;

    @Bean
public DataSource getDataSource() {
    JndiDataSourceLookup lookup = new JndiDataSourceLookup();
    try {
        DataSource dataSource = lookup.getDataSource(dataSourceString); //this always is null
        return dataSource;
    } catch (DataSourceLookupFailureException e) {
        return null;
    }
}

    @Bean
    public PropertySourcesPlaceholderConfigurer propertyPlaceHolderConfigurer() {
        return new PropertySourcesPlaceholderConfigurer();
    }
}

should AppConfig.java import the DataSourceConfig.java, I tried but I still get the Environment null. Am I missing anything? Is it right to separate the services as jar file to make them available for REST, Web app and Reports applications? Or is it advisable to have a single war with all services, rest, reports classes?

Did you try to simply add `@Autowired Environment environment;` in `AppConfig.java` and see if it is populated with `db.properties` ? — Serge Ballesta, Aug 12 '14 at 08:40
I think, Serge, that was the problem. I didn't scan that component. Now the component gets the property. — vvra, Aug 12 '14 at 09:20

Serge Ballesta · Answer 1 · 2014-08-12T09:23:56.410

AFAIK, a spring application context uses only one PropertySourcesPlaceholderConfigurer. As, the @PropertySource(value = { "classpath:db.properties" }) does not seem to populate the environment, I can see only one other solution : explicitely add it to the list of locations in AppConfig.java :

    props.setLocations(new Resource[] { new ClassPathResource(
        "application.properties"), new ClassPathResource("db.properties")});

But I must admit this is more a workaroud than a clean solution.

EDIT :

But normally, is DataSourceConfig.java is scanned by spring configuration machinery, the @PropertySource(value = { "classpath:db.properties" }) should populate the environment.

score 0 · Answer 2 · answered Sep 17 '14 at 01:19

0

you need to specify classpath within any jar, try this: @PropertySource(value = { "classpath*:db.properties" })

answered Sep 17 '14 at 01:19

Jason

526
7
9

Spring 4 - load property file inside the jar>war

2 Answers2