You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Johan Mörén (JIRA)" <ji...@apache.org> on 2013/03/15 10:24:13 UTC

[jira] [Reopened] (CAMEL-5837) Problem with nested schema imports when upgrading from 2.8.6 to 2.10.2

     [ https://issues.apache.org/jira/browse/CAMEL-5837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Johan Mörén reopened CAMEL-5837:
--------------------------------


Hello

I tried to upgrade to 2.10.4 but it still have problems resolving my imports. 

I can confirm that the first test-case works. But when i try it with a more complex import structure it fails.

I have compiled a new example project that i will attach to the issue that shows when the error occurs. I will also attach a picture showing the folder and import structure.
                
> 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
>             Fix For: 2.10.4, 2.11.0
>
>         Attachments: xsd-import_example 2.zip, xsd-import_example-reopen.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