[jira] [Issue Comment Edited] (CAMEL-4877) API-breaking changes in Validator-component

["Claus Ibsen (Issue Comment Edited) (JIRA)" <ji...@apache.org>]

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

Claus Ibsen edited comment on CAMEL-4877 at 1/15/12 3:30 PM:
-------------------------------------------------------------

Can you attach a little example of this, such as the template file which refer to the other template. Just to be sure, so we can use that for an unit test.
                
      was (Author: davsclaus):
    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: https://issues.apache.org/jira/browse/CAMEL-4877
>             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: validator://com/yyy/infra/applications/yyy-application/consumer/ws/consumer-report-request.xsd due to: src-resolve: Cannot resolve the name 'ns6:YyyReport' to a(n) 'element declaration' component.
> ...
> {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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira