camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Björn Bength <>
Subject Re: [jira] [Commented] (CAMEL-4666) support catalog entity resolver in validator-component
Date Thu, 10 Nov 2011 22:15:29 GMT
Should we make an improvement to specify a catalog file on the
validator uri? (simple but "limited" to just this catalog resolver)
Or should the validator processor and component offer a setter to
inject whatever entity resolver and make this catalog resolver a
separately configured bean. (more complex to configure but flexible).
And where to put that bean as some kind of custom entity resolver bean
glue code is necessary I think beacuse xml-resolver can't do it by
What do you think?

On Thu, Nov 10, 2011 at 10:47 PM, Björn Bength (Commented) (JIRA)
<> wrote:
>    [
> Björn Bength commented on CAMEL-4666:
> -------------------------------------
> Since I didn't find a way to configure a catalog resolver I implemented it myself to
see if would work.
> I have a patch that implements this, but as this component lives in camel-core and camel-core
seems like it's got a really bare minimum of dependencies and this patch brings in apache
xml-resolver, I didn't want to submit it as is.
>> support catalog entity resolver in validator-component
>> ------------------------------------------------------
>>                 Key: CAMEL-4666
>>                 URL:
>>             Project: Camel
>>          Issue Type: Improvement
>>          Components: camel-core
>>            Reporter: Björn Bength
>> When validating XML files against schema files, it's fairly common they import other
schemas and it's faily common they cannot be found, or reached, at the specified schema location.
Their location must therefore be rewritten, or resolved, to find the the correct schema-file
>> Apache's xml-resolver implements support for oasis and xcatalog formats.
> --
> 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