camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (Commented) (JIRA)" <>
Subject [jira] [Commented] (CAMEL-4877) API-breaking changes in Validator-component
Date Sun, 15 Jan 2012 15:30:39 GMT


Claus Ibsen commented on CAMEL-4877:

Can you attach a little example of this, such as the velocity template which refer to the
other template. Just to be sure, so we can use that for an unit test.
> API-breaking changes in Validator-component
> -------------------------------------------
>                 Key: CAMEL-4877
>                 URL:
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.9.0
>            Reporter: Johan Mörén
>             Fix For: 2.9.1, 2.10.0
> Hi, we tried to upgrade to 2.9.0 last week but ran into trouble when using the newly
moved validator component. 
> Before upgrading (running 2.8.0), having a root xsd that imported or included other xsd-files
on the class-path was no problem for us. But upgrading to 2.9.0 breaks this functionality.
Resulting in the following error 
> {code}
> ...
> Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to resolve endpoint:
due to: src-resolve: Cannot resolve the name 'ns6:YyyReport' to a(n) 'element declaration'
> ...
> {code}
> I can see in the new documentation for the validator-component that there is an new property
that you can set called *resourceResolver*. Given the name and the description of the interface
LSResourceResolver my guess is that an implementation of that interface is required to get
the old functionality back. 
> I might be wrong, but to me this is API-breaking. It would be great if you could provide
a "defalut" resourceResolver to mimic the old behavior since we rely a lot on the ability
to compose schemas via includes or imports. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message