You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Willem Jiang (JIRA)" <ji...@apache.org> on 2013/01/25 04:55:14 UTC
[jira] [Commented] (CAMEL-6013) Validator component fails on XSD
with indirect relative import
[ https://issues.apache.org/jira/browse/CAMEL-6013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13562341#comment-13562341 ]
Willem Jiang commented on CAMEL-6013:
-------------------------------------
The test case is very handy, I managed to fix the issue by letting the DefaultLSResourceResolver checking the states of relative path.
I will commit the quick fix shortly.
> Validator component fails on XSD with indirect relative import
> --------------------------------------------------------------
>
> Key: CAMEL-6013
> URL: https://issues.apache.org/jira/browse/CAMEL-6013
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.10.3
> Reporter: Peter Grant
> Attachments: camel-validator-test.tar.gz
>
>
> When using the validator component with an XSD that references a second XSD on a different path, and where the second XSD references a third XSD using a relative path, the path of the third XSD is resolved relative to the first schema rather than relative to the second. This looks similar to [CAMEL-5321], but the schemas that trigger this issue necessarily involve an additional layer of includes.
> I will include a test case that I rolled into the tarball from [CAMEL-5321].
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira