[
https://issues.apache.org/jira/browse/CAMEL-5837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13508751#comment-13508751
]
Johan Mörén commented on CAMEL-5837:
------------------------------------
>From Camels point of view, is this new behavior (since 2.9.x), considered to
>be a bug or an accepted limitation of the new implementation? We are using
>xml-schema imports extensively and this causes a lot of trouble for us. I can
>imagine ways we could get around these problems but not without extensive
>refactoring of our current projects.
regards,
Johan
> Problem with nested schema imports when upgrading from 2.8.6 to 2.10.2
> ----------------------------------------------------------------------
>
> Key: CAMEL-5837
> URL: https://issues.apache.org/jira/browse/CAMEL-5837
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.10.2
> Environment: MacOS X, java 7
> Reporter: Johan Mörén
> Assignee: Willem Jiang
> Attachments: xsd-import_example 2.zip
>
>
> Hello
> I'm experiencing trouble with the validiator component when upgrading from
> 2.8.6 to 2.10.2.
> The problem seems to be related to imported schemas that does additional
> imports (all using relative paths). XSD A importing XSD B works fine. But if
> B in turn imports XSD C. That import seems to be resolved with the base path
> of A.
> All works fine in 2.8.6 but breaks when upgrading to 2.10.2.
> I will attach an example project where you can just switch version to verify
> the scenario.
--
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
