Skip to content
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

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

Closed
gregturn opened this issue Jan 11, 2010 · 3 comments
Assignees
Milestone

Comments

@gregturn
Copy link
Member

@gregturn gregturn commented Jan 11, 2010

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:

Referenced from: commits 596946e

@gregturn
Copy link
Member Author

@gregturn gregturn commented Jan 11, 2010

Olivier Billard commented

Patch fixing this issue in a simple way.

@gregturn
Copy link
Member Author

@gregturn gregturn commented Jan 11, 2010

Arjen Poutsma commented

Applied the patch, thanks!

@gregturn
Copy link
Member Author

@gregturn gregturn commented May 4, 2012

Arjen Poutsma commented

Closing old issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants