camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Johan Mörén (JIRA) <j...@apache.org>
Subject [jira] [Commented] (CAMEL-5837) Problem with nested schema imports when upgrading from 2.8.6 to 2.10.2
Date Mon, 03 Dec 2012 07:11:58 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-5837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13508519#comment-13508519
] 

Johan Mörén commented on CAMEL-5837:
------------------------------------

Hi, yes that works but it would make the health.xsd file invalid when working with it stand-alone
in an ide like Oxygen or Intellij. Our components have been reading nested schemas from the
class-path (we package it in a war-file) before. But perhaps spring did some magic and read
it from the filesystem?

Is there anyway to get the old behavior back and still upgrade to 2.10.2?

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

Mime
View raw message