Affects Version/s: 1.0.0.M6
It does not appear that Bundlor checks the Spring-Context in the template.mf to determine where to scan for spring context XML files.
We are converting a legacy WAR, and deploying to Spring dm Server 1, so we're using the web-module format. Our project therefore has under src/main/resources only a META-INF folder (containing the MANIFEST.MF) and a MODULE-INF folder.
MODULE-INF also contains a META-INF/company/spring folder which contains my spring context files.
(In web.xml, we specify for the contextConfigLocation context-param the value of classpath*:META-INF/plateau/spring/*/.xml, and this works great at runtime.)
In the project's template.mf, if I specify any of the following, I see the Spring-Context appear in the MANIFEST.MF but the imports are not being augmented with classes specified in our spring context files.
- Spring-Context: MODULE-INF/META-INF/company/spring/*/.xml
- Spring-Context: MODULE-INF/META-INF/company/spring/*.xml
(Of course at runtime we will get an error that we're adding multiple contexts b/c of our web.xml also having a context listener - we'd take this out as part of our conversion process of the WAR. I mention this in case it is confusing Bundlor, however.)