Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Fri, 25 Jan 2013 01:49:13 +0000 (UTC)
From: "Peter Grant (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12629203.1359078149090.188539.1359078553310@arcas>
In-Reply-To: <JIRA.12629203.1359078149090@arcas>
References: <JIRA.12629203.1359078149090@arcas>
Subject: [jira] [Updated] (CAMEL-6013) Validator component fails on XSD with
 indirect relative import
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Peter Grant updated CAMEL-6013:
-------------------------------

    Attachment: camel-validator-test.tar.gz

Test case (broken) that triggers the issue.
                
> 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