SchemaCollection issue when XSD files are in the classpath, in different JAR artifacts [SWS-594]

[gregturn]

Olivier Billard opened SWS-594 and commented

Problem described in issue #509 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).

---

Affects: 1.5.8

Attachments:

• CommonsXsdSchemaCollection.diff (1.37 kB)

Referenced from: commits 596946e

[gregturn]

Olivier Billard commented

Patch fixing this issue in a simple way.

[gregturn]

Arjen Poutsma commented

Applied the patch, thanks!

[gregturn]

Arjen Poutsma commented

Closing old issues