[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

Status: Closed
Project: Spring Web Services
Component/s: XML
Affects Version/s: 1.5.8
Fix Version/s: 1.5.9

Type: Bug Priority: Minor
Reporter: Olivier Billard Assignee: Arjen Poutsma
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 2m
Original Estimate: Not Specified
Environment:

Spring WS 1.5.8, WAR file deployed in either Tomcat or Jetty.


Attachments: File CommonsXsdSchemaCollection.diff    

 Description   

Problem described in issue SWS-413 has partially been fixed.

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).



 Comments   
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

Generated at Thu Dec 14 09:49:36 UTC 2017 using JIRA 6.4.14#64029-sha1:ae256fe0fbb912241490ff1cecfb323ea0905ca5.