[SWS-594] SchemaCollection issue when XSD files are in the classpath, in different JAR artifacts Created: 11/Jan/10 Updated: 04/May/12 Resolved: 11/Jan/10
|Project:||Spring Web Services|
|Reporter:||Olivier Billard||Assignee:||Arjen Poutsma|
|Original Estimate:||Not Specified|
Spring WS 1.5.8, WAR file deployed in either Tomcat or Jetty.
Problem described in issue
Given XSD-A importing XSD-B, both in the classpath, the fix works if XSD-A and XSD-B are in the same classpath location (both in WEB-INF/classes, or in the same JAR file), but it does not work if the XSD files are located in different JAR files, for example.
The provided patch fixes this : if the imported XSD could not be resolved with the same base URI, we must keep searching in the classpath, (last statements should not be in an else block).
|Comment by Olivier Billard [ 11/Jan/10 ]|
Patch fixing this issue in a simple way.
|Comment by Arjen Poutsma [ 11/Jan/10 ]|
Applied the patch, thanks!
|Comment by Arjen Poutsma [ 04/May/12 ]|
Closing old issues