CODEWITHSUNDEEP
javaspring
Thomas Beauvais
Thomas Beauvais

Reputation: 1656

Spring ResourceLoader doesn't find resources in JAR

I am looking to create a hierarchy based on the Spring configurations. The simplest form is several "core" libraries and several "custom" projects that are able to override the beans in the "core" libraries.

When running very simply unit tests via Maven the "core" configuration isn't able to found causing the test to fail.

final Resource[] resources = applicatonContext.getResources("classpath*:core-*spring.xml");

Returns nothing. It isn't able to find the expected core-one-spring.xml or core-two-spring.xml that are located in my custom projects core dependencies.

Isn't it default behavior of Spring to look into the JARs on the classpath as well? Or is there something special I have to do?

When I run in my IDE (IntelliJ) the tests pass perfectly because the entire project is loaded and they are just files that Spring can find.

UPDATE

Spring is able to find the files if I add them explicitly without wildcards.

@ContextConfiguration({"classpath:core-one-spring.xml", "classpath:core-two-spring.xml", "classpath:custom-spring.xml", "classpath:test-spring.xml"})

or 

final Resource[] resources = custom.getResources("classpath:core-one-spring.xml");

Upvotes: 2

Views: 3545

Answers (1)

Emerson Farrugia
Emerson Farrugia

Reputation: 11363

From the manual

Please note that " classpath*:" when combined with Ant-style patterns will only work reliably with at least one root directory before the pattern starts, unless the actual target files reside in the file system. This means that a pattern like " classpath*:*.xml" will not retrieve files from the root of jar files but rather only from the root of expanded directories. This originates from a limitation in the JDK’s ClassLoader.getResources() method which only returns file system locations for a passed-in empty string (indicating potential roots to search).

Upvotes: 3

Related Questions