Details
-
Improvement
-
Status: Resolved
-
Trivial
-
Resolution: Fixed
-
2.10.1
-
Moderate
Description
As far as I understand, the validator "component" in Camel can only use schemas deployed as file within the classpath (typically the deployed application - ear/war/jar whatever have you) or some file/http resource.
Sometimes you might want to load the schema a bit more dynamically, I.E. from some datasource or semi-generate something on the fly. My suggestion is that a schema could be supplied in a propery or a header to the validator.
I wrote such an extension to the validator and could probably rewrite it easily as a patch to the regular validator. Do you think people want to use such a feature and that it might be good to have in Camel? Should I submit a patch?