-
Notifications
You must be signed in to change notification settings - Fork 38.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
classpath*: is no longer finding resources with <import resource=""/> [SPR-6351] #11017
Comments
Klaus Lehner commented Not only that this feature isn't working any more, the error message that comes up now is quite confusing: We have something like: <import resource="classpath*:WEB-INF/dao-context-*.xml"/> respectively just: <import resource="classpath*:/WEB-INF/dao-context.xml"/> The error message that comes up when starting the server is astonishing: java.io.FileNotFoundException: URL [jndi:/localhost/WEB-INF/] cannot be resolved to absolute file path because it does not reside in the file system: jndi:/localhost/WEB-INF/ And that although there is no use of jndi anywhere in our server code. |
Sam Brannen commented FYI: the inclusion of the jndi resource lookup is likely the result of running your web application in Tomcat. |
Scott Andrews opened SPR-6351 and commented
Between RC1 and RC2, classpath*: file paths stopped working. In a web app context, I am importing a set of spring contexts that form a plugin system. None of the files that match this pattern are detected
<import resource="classpath*:META-INF/insight/insight-plugin-*.xml" />
Removing the wild card and hard coding the path also does not pickup the files.
<import resource="classpath*:META-INF/insight/insight-plugin-springmvc.xml" />
Replacing the classpath*: with classpath: it is able to find the file.
<import resource="classpath:META-INF/insight/insight-plugin-springmvc.xml" />
Using classpath: with a wild card only imports a single resource. (appears to be the first match alphabetically)
<import resource="classpath:META-INF/insight/insight-plugin-*.xml" />
Affects: 3.0 RC2
Issue Links:
1 votes, 0 watchers
The text was updated successfully, but these errors were encountered: