Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Mon, 3 Dec 2012 07:11:58 +0000 (UTC)
From: =?utf-8?Q?Johan_M=C3=B6r=C3=A9n_=28JIRA=29?= <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <1663979798.52204.1354518718481.JavaMail.jiratomcat@arcas>
In-Reply-To: <416893731.44887.1354276798317.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (CAMEL-5837) Problem with nested schema imports
 when upgrading from 2.8.6 to 2.10.2
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


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

Johan M=C3=B6r=C3=A9n commented on CAMEL-5837:
------------------------------------

Hi, yes that works but it would make the health.xsd file invalid when worki=
ng with it stand-alone in an ide like Oxygen or Intellij. Our components ha=
ve 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 filesy=
stem?

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

regards,
Johan
               =20
> 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=C3=B6r=C3=A9n
>            Assignee: Willem Jiang
>         Attachments: xsd-import_example 2.zip
>
>
> Hello
> I'm experiencing trouble with the validiator component when upgrading fro=
m 2.8.6 to 2.10.2.=20
> 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 i=
f B in turn imports XSD C. That import seems to be resolved with the base p=
ath of A.=20
> 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 ver=
ify the scenario. =20

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira