Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Sun, 15 Jan 2012 15:32:39 +0000 (UTC)
From: "Claus Ibsen (Issue Comment Edited) (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: 
 <1953114435.42767.1326641559438.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <934995290.21713.1326120999330.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Issue Comment Edited] (CAMEL-4877) API-breaking changes in
 Validator-component
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


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

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 re=
fer to the other template. Just to be sure, so we can use that for an unit =
test.
               =20
      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.
                 =20
> 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=C3=B6r=C3=A9n
>             Fix For: 2.9.1, 2.10.0
>
>
> Hi, we tried to upgrade to 2.9.0 last week but ran into trouble when usin=
g the newly moved validator component.=20
> Before upgrading (running 2.8.0), having a root xsd that imported or incl=
uded 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=20
> {code}
> ...
> Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to res=
olve endpoint: validator://com/yyy/infra/applications/yyy-application/consu=
mer/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 n=
ame and the description of the interface LSResourceResolver my guess is tha=
t an implementation of that interface is required to get the old functional=
ity back.=20
> I might be wrong, but to me this is API-breaking. It would be great if yo=
u could provide a "defalut" resourceResolver to mimic the old behavior sinc=
e we rely a lot on the ability to compose schemas via includes or imports.=
=20

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira