[
https://issues.apache.org/jira/browse/CAMEL-13047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
W.Y updated CAMEL-13047:
------------------------
Description:
When using the validator component with an XSD that references (import/include)
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.
I found it it same bug ticket reported , although it stated it is fixed already
at camel 2.10, but it does not work for us when we use >=camel 2.22. The
problem is reproducable with testcase from
https://issues.apache.org/jira/browse/CAMEL-5321 . i modified it and put it
here again for you to reproduce the problem. thanks and rgds
was:
Validator Component Fails on XSD with file Relative Imports or include
When using the Validator Component with an XSD file from a Jar that contains a
relative import, the component will throw a FileNotFoundException.
This is due to the ObjectHelper.loadResourceAsStream(String) operation
attempting to load the classpath resource using file path semantics that will
not resolve canonically,
I found it it same bug ticket reported , although it stated it is fixed already
at camel 2.10, but it does not work for us when we use >=camel 2.22. The
problem is reproducable with testcase from
https://issues.apache.org/jira/browse/CAMEL-5321 . i modified it and put it
here again for you to reproduce the problem. thanks and rgds
> Validator Component Fails on XSD with file Relative Imports or include
> -----------------------------------------------------------------------
>
> Key: CAMEL-13047
> URL: https://issues.apache.org/jira/browse/CAMEL-13047
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.22.0, 2.22.1, 2.22.2
> Reporter: W.Y
> Priority: Major
> Attachments: camel-validator-test.zip
>
>
> When using the validator component with an XSD that references
> (import/include) 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.
> I found it it same bug ticket reported , although it stated it is fixed
> already at camel 2.10, but it does not work for us when we use >=camel 2.22.
> The problem is reproducable with testcase from
> https://issues.apache.org/jira/browse/CAMEL-5321 . i modified it and put it
> here again for you to reproduce the problem. thanks and rgds
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
