Hi,
We are heavily relying on the ResourceLoader and more specifically the org.springframework.core.io.support.PathMatchingResourcePatternResolver. In a legacy codebase that we own, we are using this call very often: applicationContext.getResources("classpath*:**/some-file-pattern.xml") or any other type of pattern.
Since version 6.2.4 we clearly see a difference in behavior here. Compared to version 6.2.3 we observe that now nothing is returned while it was returning the expected resources in the previous version.
We also see a difference in behavior when running locally from IntelliJ compared to running the final WAR. Running locally in IntelliJ (which is obviously more 'File based' scanning than 'Jar based' scanning) everything works. Running in the final WAR, everything fails.
As it only occurs in the final runtime, it is very difficult to analyze the Spring code to pinpoint where the difference in behavior is caused. We do see changes in org.springframework.core.io.support.PathMatchingResourcePatternResolver as of 6.2.x and a small Exception change in 6.2.4, but we couldn't point to that 100% as being the root cause.
Can you help us out here? What could have caused this difference in behavior ?
Hi,
We are heavily relying on the
ResourceLoaderand more specifically theorg.springframework.core.io.support.PathMatchingResourcePatternResolver. In a legacy codebase that we own, we are using this call very often:applicationContext.getResources("classpath*:**/some-file-pattern.xml")or any other type of pattern.Since version
6.2.4we clearly see a difference in behavior here. Compared to version6.2.3we observe that now nothing is returned while it was returning the expected resources in the previous version.We also see a difference in behavior when running locally from IntelliJ compared to running the final WAR. Running locally in IntelliJ (which is obviously more 'File based' scanning than 'Jar based' scanning) everything works. Running in the final WAR, everything fails.
As it only occurs in the final runtime, it is very difficult to analyze the Spring code to pinpoint where the difference in behavior is caused. We do see changes in
org.springframework.core.io.support.PathMatchingResourcePatternResolveras of 6.2.x and a small Exception change in 6.2.4, but we couldn't point to that 100% as being the root cause.Can you help us out here? What could have caused this difference in behavior ?