[
https://issues.apache.org/jira/browse/CAMEL-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13148312#comment-13148312
]
Björn Bength commented on CAMEL-4666:
-------------------------------------
Yes, i sent a separate email to the dev-list with this question:
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
itself.
What do you think?
The problem with the more flexible solution is it requires extensive work by
the end-user as he need to write this wrapper-code and then configure it a lot
more.
Compare with for example "xjc" tool or the "maven-jaxb2-plugin" where you can
specify a catalog file. Plain and simple.
If this glue code can be provided in another camel module, it would be a little
less problem. Just a lot more configuration for the end-user.
I'm of course open to any solution to this problem because now the validation
component is mostly useless to all my use cases.
> support catalog entity resolver in validator-component
> ------------------------------------------------------
>
> Key: CAMEL-4666
> URL: https://issues.apache.org/jira/browse/CAMEL-4666
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Björn Bength
> Assignee: Christian Müller
> Attachments: validator-catalog.patch
>
>
> 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 elsewhere.
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
